Skip to main content
Glama

veritas-8183-3star-rating-seal

verify_onchain_escrow_status

Read-onlyIdempotent

[Public] Proof that this service is real: verified Base contract (Sourcify), signed agent passport and fee terms. Example: call with {}.

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": "verify_onchain_escrow_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeReceiptsNoInclude Sourcify and LEGION Merkle inclusion receipts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / includeReceipts
      Added value: +{
      +  "description": "Include Sourcify and LEGION Merkle inclusion receipts.",
      +  "examples": [
      +    true
      +  ],
      +  "type": "boolean"
      +}
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds that the tool is public and lists the kinds of proof returned (Sourcify-verified contract, signed passport, fee terms), but it does not disclose response format, latency, or any rate-limit/auth behavior.

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 compact and front-loads the key claim with the public marker and proof elements. The example is useful, though the phrase 'Proof that this service is real' is slightly marketing-like and could be more precise about the verification action.

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

Completeness3/5

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

For a low-complexity, one-parameter read-only tool with rich annotations, the description covers the basic purpose and proof types. However, with no output schema, the description should do more to explain what the returned proof looks like or what the agent can expect from the response.

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?

There is one optional parameter, includeReceipts, and the schema description coverage is 100%, so the schema fully documents it as including Sourcify and LEGION Merkle inclusion receipts. The description's example of calling with {} implies the default omits receipts, but it does not add meaning beyond the schema. Baseline 3 applies when schema coverage is high.

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 says it provides proof that the service is real by showing a verified Base contract, signed agent passport, and fee terms. However, it does not clearly state the action (verify) or explicitly connect to 'on-chain escrow status' as the tool name implies, and it does not distinguish this tool from sibling audit or trust-check tools.

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 only usage hint is 'Example: call with {}', which shows invocation but not when to use this tool versus alternatives. There is no guidance on prerequisites, when-not-to-use, or how it relates to the many sibling escrow and trust tools.

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.