Skip to main content
Glama

create_transaction_record_evidence_challenge

Create a private read-only evidence challenge for an operation or protected job. Sign the exact returned message locally. No payment or state transition.

Input Schema

NameRequiredDescriptionDefault
idYes
kindYes
walletYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 does disclose meaningful traits: the challenge is private and read-only, causes no payment and no state transition, and the returned message must be signed locally. It omits other operationally relevant behavior such as challenge expiry, single-use semantics, and what the returned payload contains.

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 purpose followed by the required next step and the side-effect disclaimer. Every sentence carries information, though the compression leaves key schema distinctions unresolved rather than over-explaining.

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?

The input schema is non-trivial (oneOf branches, a uuid-or-0x-hash pattern, an enum), there are no annotations and no output schema, yet the description says nothing about how id and kind must correspond or what the challenge response looks like. For a three-required-parameter challenge tool with zero parameter documentation, more disclosure is needed.

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 three required parameters, so the description must compensate and largely does not. "operation or protected job" loosely maps to the kind enum and "locally" hints that wallet is the signing address, but the id parameter and the uuid-vs-0x hash distinction are never explained.

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 specific verb and resource ("create ... evidence challenge") plus scope ("for an operation or protected job"), which lets an agent distinguish this from the read_* evidence siblings. It does not differentiate itself from the near-identically named create_transaction_evidence_challenge, leaving ambiguity among the many create_*_challenge siblings.

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 phrase "for an operation or protected job" implies the applicable context, and "Sign the exact returned message locally" implies a follow-up signing flow. There is no explicit when-not guidance and no named alternative tool, so the agent must infer the boundary against sibling challenge creators.

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