Skip to main content
Glama

cite_contract

Cite a signed meaning contract on a dispute

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cite_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNo
stageNo
contractNo
worker_claimedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.6/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden. It does not disclose whether citing is a read or a mutation, whether the citation persists, what permissions are needed, or what a successful citation returns.

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

Conciseness2/5

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

The single sentence is short, but its brevity comes from under-specification rather than efficiency. It has no waste to cut, but it also supplies almost no information.

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

Completeness1/5

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

Four undocumented parameters include a nested object, and there are no annotations and no output schema. The description therefore provides none of the context an agent needs to invoke this tool correctly.

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?

Schema description coverage is 0% across four parameters, including a nested 'contract' object, and the description explains none of them. The meanings of 'term', 'stage', and 'worker_claimed' are entirely undocumented anywhere.

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

Purpose3/5

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

It names a specific verb ('cite') and resource ('contract') and mentions the dispute context, which faintly separates it from verify_contract. But 'signed meaning contract on a dispute' is domain jargon that an agent cannot resolve into a concrete operation, and the title is null.

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

Usage Guidelines1/5

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

There is no guidance on when to use this rather than verify_contract or handshake, no prerequisites, and no indication of what a 'dispute' entails or when citing is appropriate.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources