Zorqelio — Data Reliability for AI Agents

contract_create

Create a private, reusable, versioned data contract for an AI-agent workflow. Returns a one-time access token; store it securely because it cannot be retrieved later.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspaceToken": "<workspaceToken>",
      "name": "<name>",
      "schema": "<schema>"
    },
    "name": "contract_create"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`schema`	Yes
`description`	No
`operationId`	No
`workspaceToken`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

C2.9/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden and does disclose an important trait: it returns a one-time access token that cannot be retrieved later and must be stored securely. However, it does not explain permissions, side effects, duplicate-name behavior, validation requirements, or what happens to existing versions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two focused sentences with zero obvious waste. It front-loads the creation purpose and follows with the critical token-handling warning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has five parameters, no annotations, no output schema, and 0% schema description coverage, so the description should compensate more. It gives a useful token warning but omits parameter meanings and key behavioral details needed to invoke a contract-creation tool confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are five parameters with 0% schema description coverage, and the description explains none of them. It does not clarify workspaceToken, name, schema format, description, or operationId, leaving parameter meaning entirely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb, "Create," and clearly identifies the resource as a "private, reusable, versioned data contract for an AI-agent workflow." It is understandable without opening the schema, though it does not explicitly distinguish this from sibling tools such as contract_publish or contract_validate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides the general context of creating a contract for an AI-agent workflow, but it gives no when-to-use guidance, no exclusions, and no alternatives. An agent must infer that this is the tool for new contract creation rather than publishing, validating, retrieving, or comparing contracts.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Zorqelio — Data Reliability for AI Agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?