Skip to main content
Glama

veritas-8183-3star-rating-seal

audit_api_sla_escrow

Idempotent

[Private] Did the paid API or oracle deliver what it promised? Checks latency, required JSON fields and data freshness. Example: observedLatencyMs=38, maxLatencyMs=200.

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": {
      "apiResponsePayload": "<apiResponsePayload>"
    },
    "name": "audit_api_sla_escrow"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxLatencyMsNoMaximum allowed SLA latency in milliseconds.
requiredKeysNoMandatory top-level JSON keys required by the SLA.
observedLatencyMsNoMeasured round-trip response latency in milliseconds.
apiResponsePayloadYesParsed JSON payload returned by the oracle or API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / apiResponsePayload / description
      Added value: +"Parsed JSON payload returned by the oracle or API."
    • addedInput schema / properties / maxLatencyMs / description
      Added value: +"Maximum allowed SLA latency in milliseconds."
    • addedInput schema / properties / observedLatencyMs / description
      Added value: +"Measured round-trip response latency in milliseconds."
    • addedInput schema / properties / requiredKeys / description
      Added value: +"Mandatory top-level JSON keys required by the SLA."
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

The annotations declare readOnlyHint=false with destructiveHint=false and idempotentHint=true, implying the call persists some result, yet the description's 'Checks...' framing reads as a pure read and never says an audit record is written or where. It also leaves the 'data freshness' check unexplained — no parameter supplies a freshness threshold, so the agent cannot tell how that criterion is derived (presumably from payload timestamps). With no output schema, the description should say what a pass/fail result looks like but does not.

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?

Three short sentences, front-loaded with the purpose question and followed by the concrete checks and a numeric example. The bracketed '[Private]' tag and the example both earn their space; nothing is padded.

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 four-parameter tool with a nested payload object and no output schema, the description covers what is inspected but not the outcome shape, the failure/refund consequence, or the freshness logic. An agent could call it correctly but could not predict or interpret the result without trial.

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?

Schema coverage is 100%, so all four parameters are already documented, and the description's example (observedLatencyMs=38, maxLatencyMs=200) only illustrates the latency pair. It adds no guidance on requiredKeys matching semantics or on what happens when apiResponsePayload lacks required keys, so the baseline 3 applies.

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 rhetorical question plus the follow-up 'Checks latency, required JSON fields and data freshness' names a specific verb (audit/check) and resource (paid API or oracle response against an SLA). The scope ('paid API or oracle') is narrow enough to separate it from the GPU, inference, RAG and backtest escrow siblings, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

Usage is implied by 'Did the paid API or oracle deliver what it promised?' — an agent can infer this runs after receiving a payload to verify SLA compliance. However, there is no explicit when-to-use, no when-not-to-use, and no routing to alternatives such as verify_onchain_escrow_status or claim_escrow_timeout_refund when the audit fails.

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.