Skip to main content
Glama

Verify a listening session and get a signed receipt

verify_session

Submit pre/post HRV segments (RMSSD, IBI, source) for a paid session and receive an Ed25519-signed receipt. Not paywalled.

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": {
      "session_id": "<session_id>",
      "agent_id": "<agent_id>",
      "pre": "<pre>",
      "post": "<post>"
    },
    "name": "verify_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
preYes
postYes
agent_idYes
album_idNo
track_idNo
payment_txNo
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full disclosure burden. It does add genuine context (Ed25519 signature, receipt as return value, no paywall), but says nothing about whether state is persisted, what happens when verification fails, idempotency on repeated session_id, or whether the receipt is cached — all important for a verify operation with seven parameters.

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?

Two short sentences with the action and the return value front-loaded; nothing is padded. The dangling 'Not paywalled' fragment is efficient but cryptic enough to cost a point.

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 seven parameters, four required, nested object payloads, zero schema coverage, no annotations, and no output schema, the description is far too thin. An agent cannot determine the expected pre/post structure, when the optional identifiers are needed, or how failures surface.

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% and pre/post are untyped nested objects, so the description's mention of RMSSD, IBI, and source is the only field-level documentation available. It leaves agent_id, album_id, track_id, payment_tx, and session_id entirely unexplained, and the payment_tx parameter actively conflicts with the 'Not paywalled' claim without clarification.

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 description names a concrete action (submit pre/post HRV segments) and a concrete result (an Ed25519-signed receipt), and the 'Not paywalled' clause implicitly separates it from the purchase_* siblings. It is clear what the tool does, though it never explicitly names an alternative tool.

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 only routing signal is the terse 'Not paywalled' phrase, which hints that this call does not require payment, unlike purchase_album/purchase_track. There is no explicit when-to-use statement, no prerequisites, and no guidance on when to prefer get_track_evidence or the purchase siblings instead.

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.