Skip to main content
Glama

Stream Presence — Receipt Verifier

Check issuer standing

issuer_standing
Read-onlyIdempotent

Whether a did:key is a registered receipt issuer in good standing: class, status, daily cap, any signed revocation, and its receipt count in the log. An unregistered DID is reported as such.

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": {
      "did": "<did>"
    },
    "name": "issuer_standing"
  }
}

Input Schema

NameRequiredDescriptionDefault
didYesThe issuer's did:key (did:key:z…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered without the description. The description does add one piece of behavioral context beyond the annotations: an unregistered DID is reported as such rather than erroring, which tells the agent how to handle the negative case. However it says nothing about output shape/format (units of daily cap, revocation encoding), and there is no output schema to fill that gap.

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

Conciseness5/5

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

Two sentences, front-loaded with the core question, then the returned attributes, then the negative case. No filler, no restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool whose annotations cover safety, the description covers purpose, what fields come back, and the unregistered-DID case. What it omits is return formatting details, which matter more here because there is no output schema, keeping it from a 5.

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

Parameters4/5

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

Only one parameter, and the schema documents it at 100% coverage including the required did:key format. The description adds no syntax or constraint detail beyond the schema, but with a single fully-documented parameter little more is needed.

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 lookup ('whether a did:key is a registered receipt issuer in good standing') and enumerates exactly the attributes returned: class, status, daily cap, signed revocation, receipt count. An agent can tell this is an issuer-status lookup rather than a receipt read. It does not explicitly name the sibling it differs from (get_receipt, verify_receipt), so it stops short of a 5.

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 only implied: an agent can infer it should call this to vet an issuer before trusting its receipts, but there is no stated when-to-use, when-not-to-use, or precondition (e.g., call before get_receipt/verify_receipt). No alternative tool is named.

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