Skip to main content
Glama

create_transaction_evidence_challenge

Request a private Work Ticket evidence read challenge without revealing ticket ownership. Sign the exact returned message locally. No payment or work action.

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": {
      "buyer": "<buyer>",
      "ticketId": "<ticketId>"
    },
    "name": "create_transaction_evidence_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerYes
ticketIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 the key flow: a challenge is returned, the caller signs the exact message locally, and ownership is not revealed. It omits what the challenge contains, expiry/replay semantics, and whether any server state is created—gaps that matter for an unannotated tool.

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, front-loaded sentences with no filler; the privacy property and the signing step come first. The final fragment 'No payment or work action.' is terse to the point of ambiguity but still earns its place as a scope signal.

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 two-required-parameter challenge-creation tool with no annotations and no output schema, the description covers the required follow-up (local signing of the returned message) but not the parameter meanings, challenge lifetime, or signature expectations. Adequate to start a call, not complete enough to call confidently.

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%, so the description should explain the two required parameters, but it never mentions 'buyer' or 'ticketId'. The schema only supplies regex/uuid constraints, leaving the meaning of each argument (whose address, which ticket) to inference.

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?

States a concrete verb and resource: requesting a private Work Ticket evidence read challenge, and adds the distinguishing property that it does not reveal ticket ownership. An agent can tell it creates a signing challenge rather than reading evidence, though it never names the sibling read tools it differs from.

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?

The line 'No payment or work action' implicitly scopes it as a read-access challenge rather than a paid or state-changing flow, which helps. However, there is no explicit statement of when to choose this over sibling challenge creators (e.g. grant or receipt challenges) or the direct read 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.

Resources