Skip to main content
Glama
Sign In
Nagora MCP server

Nagora MCP server

Official
by m-flex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get the signed receipt

get_receipt

Retrieve a cryptographically signed receipt for a completed order after escrow release, including seller Nano address, payout block hash, and KMS signature.

Instructions

Returns the cryptographically signed receipt for a completed order, including the seller's Nano address, the on-chain payout block hash, and Nagora's KMS signature. Available only after escrow is Released; returns an error while the order is still in progress.

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": {
      "orderId": "<orderId>"
    },
    "name": "get_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYesOrder ID to fetch the receipt for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It discloses the state dependency (escrow Released), the error behavior while in progress, and the contents of the receipt. It doesn't explicitly state it is read-only, but 'get' implies a safe operation and the description focuses on retrieval.

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 main purpose and contents, followed by the availability condition. No redundant phrasing or fluff.

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?

Covers the essential aspects: what is returned, when it is available, and error behavior. It lacks an explicit return format, but no output schema exists; the information is sufficient for a simple one-parameter retrieval tool.

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?

Schema coverage is 100%—orderId is described as 'Order ID to fetch the receipt for'. The description adds no extra semantic details about the parameter, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it returns the cryptographically signed receipt for a completed order, specifying contents (seller's Nano address, payout block hash, KMS signature). This distinctively separates it from siblings like get_order, which would fetch order details.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit condition: available only after escrow is Released, and returns an error during progress. This gives a clear when-to-use signal. It does not name alternative tools, but the purpose is distinct from the sibling set, making the guidance sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools