Skip to main content
Glama
Sign In
Nagora MCP server

Nagora MCP server

Official
by m-flex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get listing detail

get_listing

Retrieve a single marketplace listing by its ID to view full details, including variants, delivery options, and pricing, and obtain the quoted Nano total for escrow-protected purchases.

Instructions

Fetch a single listing by ID. No API key required. Returns full detail including variants, delivery options, and pricing. Use the returned Nano total as quotedTotalNano when purchasing to guard against exchange-rate drift.

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": {
      "listingId": "<listingId>"
    },
    "name": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
listingIdYesListing ID from search_listings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses that no API key is required, that the operation is a read-only fetch, and that output includes variants, delivery options, pricing, and a Nano total. It adds practical behavioral guidance by telling agents to use the Nano total as quotedTotalNano to guard against exchange-rate drift.

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?

Three sentences, each carrying distinct value: core action, authentication requirement, and output/usage guidance. The description is front-loaded and contains no filler or redundant restatement of the tool name.

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

Completeness5/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 with no output schema, the description is complete enough. It covers what the tool returns, the auth context, and how the return value should be used downstream. The input origin is documented in the schema, so no critical context is missing.

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?

The schema already provides full 100% coverage for listingId, including its format and source. The description only says 'by ID' and does not add parameter-specific meaning beyond the schema. Baseline 3 applies because the schema does the heavy lifting.

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?

The description uses a specific verb ('Fetch') and resource ('a single listing by ID'), clearly distinguishing it from search_listings. The title reinforces the same purpose. An agent can tell exactly what this tool does without ambiguity.

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?

The description implies the tool is used after search_listings by noting the listingId comes from search_listings in the schema, and it connects to the purchase flow. It provides clear context but does not explicitly name alternatives or when-not-to-use conditions.

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