📐
🛠️ Create
LV2 · Toolooo Standard
Explore → See → Understand → ActUnderstand it. Feature Level describes the depth of the tool experience.

MCP Tool Contract Builder

Create bounded MCP input/output schemas with separate approval, scope, retry and failure guidance.

EngineeringAIAPISecurityValidationPlanning
🔒Your tool inputs are processed in your browser and are not uploaded or sent to analytics.

Define the MCP tool separately from implementation safeguards. No server is connected or generated. Use fictional examples; copied/downloaded JSON contains the contract text and enum/default literals you enter.

2/40 fields across active schemas.

Input fields

Input field 1 · document_id · string · required
Input field 1
Constraints and optional default

Defaults document an optional value; they do not fill missing input or grant authorization. Formats are annotations here; configure format assertions in your validator.

Output fields

Output field 1 · content · string · required
Output field 1
Constraints and optional default

Defaults document an optional value; they do not fill missing input or grant authorization. Formats are annotations here; configure format assertions in your validator.

Declared behavior, scope and retry plan
Data access
External side effects

Select all that apply; an empty selection declares no external effects.

All answers are declarations, not detected enforcement. Classifications and review warnings use behavior plus field shapes; they cannot prove implementation safety.

Builder limits and protocol reference

Maximum 40 fields across active schemas, two field levels, 20 scalar enum values per field and 60 KB MCP JSON. No raw schemas, references, nested arrays, arbitrary patterns or complete JSON Schema editing. Defaults are optional scalar annotations; formats need validator configuration. Field names use a conservative ASCII subset. Review names, sensitivity and instruction warnings manually; heuristics do not establish intent or completeness.

Approval, failure categories, retry and idempotency guidance live only in the safety plan. No invented MCP approval/idempotency fields or enforcement claims. Check tool-name uniqueness within your server separately. MCP tool specification.

What this tool does and why

Before you start

What

Create bounded MCP input/output schemas with separate approval, scope, retry and failure guidance.

Why

Explicit field shapes and side-effect declarations reduce ambiguity before implementation. A schema describes data; authorization, approval and retry controls still require independent enforcement.

Your Result and Action update in the tool as you change its inputs.

Model note

This browser-side model explains the inputs you choose. Check an important decision against the real system, brief, or production constraints.

Next

Use the result to choose a connected next move.

MCP Security DoctorReview MCP tool and server JSON for risky capabilities, broad permissions, approval gaps and sensitive data signals.
How this tool stays honest

How it works

Build a tool definition using a bounded JSON Schema 2020-12 editor. Review declared side effects, field constraints, sensitive-data signals and contract-quality findings. Copy MCP JSON separately from Toolooo safety guidance; no MCP server is generated, connected or certified.

Assumptions

The tool runs in your browser and models the information you provide. It does not know facts outside that model.

Limitations

MCP tool-definition profile with a bounded object-root JSON Schema 2020-12 subset. No live MCP validation, server generation, reference resolution or security certification. Field/sensitivity warnings are heuristic; runtime validators, authorization, approvals and deduplication require implementation.

Understand MCP Tool Contract Builder

What this tool helps you understand

Build a tool definition using a bounded JSON Schema 2020-12 editor. Review declared side effects, field constraints, sensitive-data signals and contract-quality findings. Copy MCP JSON separately from Toolooo safety guidance; no MCP server is generated, connected or certified.

When to use it

Before implementing or exposing an agent-callable capability.

Try a scenario

Compare a constrained public document reader with a refund operation. Inspect required fields, bounded amounts, exact approval and payload-bound deduplication; copy the MCP definition and review it locally in MCP Security Doctor.

How to read the result

PASS means supported builder checks passed, not that implementation is secure. Resolve FAIL before export and review WARN findings. Keep the MCP definition separate from Toolooo safety metadata; copy JSON for a local MCP Security Doctor review.

Assumptions and limits

MCP tool-definition profile with a bounded object-root JSON Schema 2020-12 subset. No live MCP validation, server generation, reference resolution or security certification. Field/sensitivity warnings are heuristic; runtime validators, authorization, approvals and deduplication require implementation.

Toolooo is part of Khizooology, created byKhizar Imtiaz (khizooo).