Skip to main content
Glama

request_review

Provider: seal {payload,salt,pad} to the selected reviewer using AAD agent-market/review|taskId|claimId|commitment and send the matching Deliver signature. Ciphertext only.

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": {
      "claimId": "<claimId>",
      "commitment": "<commitment>",
      "box": "<box>",
      "nonce": "<nonce>",
      "deadline": "<deadline>",
      "signature": "<signature>"
    },
    "name": "request_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
boxYes
nonceYes
claimIdYes
deadlineYes
signatureYes
commitmentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/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 burden, and it does disclose non-obvious mechanics: the AAD construction string (agent-market/review|taskId|claimId|commitment) and the requirement to supply a matching Deliver signature. It says nothing about permissions, cost, failure modes, or reversibility, leaving significant gaps for a mutation-style operation.

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

Conciseness3/5

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

It is short, but the front-loaded 'Provider:' label is ambiguous and the crypto notation is compressed to the point of being opaque. Little waste, but the ordering does not prioritize orientation for the agent.

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?

For a tool with six required parameters, a nested free-form object, zero schema descriptions, no annotations, and no output schema, the description is far from sufficient. It explains the AAD and signature pairing but leaves most call-construction details to inference.

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

Parameters2/5

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

Schema description coverage is 0% across six required parameters, several cryptically named (box, nonce, commitment). The description helps by tying claimId and commitment to the AAD, but never maps payload/salt/pad to the box object, never explains nonce, deadline, or signature format, and mentions a taskId that is not even in the schema.

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

Purpose2/5

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

The description states a mechanical action ('seal {payload,salt,pad} to the selected reviewer ... and send the matching Deliver signature'), but the 'Provider:' prefix and dense crypto jargon obscure the plain purpose: requesting a review. An agent cannot readily distinguish this from siblings like deliver, decide_review, or submit_quote without outside knowledge.

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?

There is no indication of when this tool should be used, what must precede it (e.g., claim_task producing claimId/commitment), or how it differs from deliver or decide_review. The only directional cue is the terse 'Ciphertext only' constraint.

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