Groundtruth: site inspections, photos and pickups; court and property records retrieval

Change a requirement by field

edit_requirement

Idempotent

Set fields by name ({"op":"set","values":{...}}, an empty value clears) or change the list ({"op":"add"|"update"|"remove"|"replace", ...}), exactly as given: no reading. Use it to answer the open question when the answer is a value.

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": {
      "slug": "<slug>",
      "id": "<id>",
      "token": "<token>",
      "ops": "<ops>"
    },
    "name": "edit_requirement"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The requirement id from an earlier answer
`ops`	Yes
`slug`	Yes	The service, from list_propositions
`op_id`	No
`token`	Yes	Its private token (also the receipt token of the request it is sent as); keep it private
`base_revision`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

C2.8/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that an empty value clears a field and that operations apply "exactly as given: no reading," which is meaningful behavioral context, but it omits what happens on missing requirements, concurrency conflicts, or failed ops.

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

Conciseness4/5

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

The description is short and front-loads the most important op syntax before the usage hint. It is dense and somewhat cryptic, especially the inline JSON fragments and "no reading," but there is little wasted wording.

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?

This is a mutation tool with six parameters and no output schema. The description covers the ops payload but is silent on base_revision concurrency semantics, op_id behavior, and what a successful edit returns, which are material gaps for an agent invoking it correctly.

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

Parameters3/5

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

The description gives substantial detail for the opaque ops parameter, including set/add/update/remove/replace forms and empty-value clearing. However, with only 50% schema description coverage across six parameters, it leaves base_revision, op_id, and the overall id/token relationship unexplained beyond what the schema already says.

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?

The description explains the mechanics of the ops payload (setting fields by name or changing the list) but never plainly states that it edits an existing requirement. The title helps, but the description alone leaves the overall purpose somewhat procedural rather than declarative, and it does not distinguish itself from siblings like get_requirement or send_requirement.

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?

Only a narrow usage hint is provided: "Use it to answer the open question when the answer is a value." There is no explicit guidance on when not to use it, and no named alternatives such as answer_remedy, interpret_requirement, or send_requirement are given.

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

All Groundtruth: site inspections, photos and pickups; court and property records retrieval 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?