Skip to main content
Glama

Hummingbird

Check an offer

offer_status
Read-only

Returns the current state and expiry of an offer, using its private receipt.

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": {
      "receipt": "<receipt>"
    },
    "name": "offer_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptYesThe private one-time receipt returned by make_offer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the receipt is a secret and that state and expiry are what come back, but it leaves an important ambiguity unaddressed: whether the 'one-time' receipt is consumed or invalidated by checking status.

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?

One sentence, front-loaded with the resource and return content, followed by the input qualifier. Nothing extraneous and nothing buried.

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?

There is no output schema, so the description carries the burden of explaining return values; it names 'state' and 'expiry' but does not enumerate possible states or say what is returned for an invalid or expired receipt. For a simple read tool with clear annotations this is adequate, but not fully complete.

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

Parameters3/5

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

With a single parameter at 100% schema coverage, the schema already defines the receipt as the one-time value returned by make_offer. The description restates 'private receipt' without adding format, validation, or error semantics beyond the schema.

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?

Specific verb ('Returns') plus resource ('current state and expiry of an offer') with the input identified ('using its private receipt'). This clearly distinguishes it from the mutating siblings make_offer and withdraw_offer, though it never names them explicitly.

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: the receipt comes from make_offer, so this is the follow-up lookup. There is no explicit statement of when to call it, whether it can be polled repeatedly, or what to do if the receipt is unknown or expired.

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.