Skip to main content
Glama
Procurement MCP

Procurement MCP

by belikh

get_offer_detail

Fetch full details for one product offer by ID, using live data from supported marketplaces and recent-search data for others, to verify price, shipping, and seller information.

Instructions

Fetch one offer by id.

taobao, tmall, 1688, jd and pdd ids are fetched live from TMAPI, and ebay_au
ids from the eBay Browse API. Other marketplaces have no detail endpoint:
the offer is returned as it was in the most recent search that contained it.

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": {
      "offer_id": "<offer_id>"
    },
    "name": "get_offer_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
offer_idYesOffer id from search_offers, e.g. taobao:123456 or ebay_au:v1|1234|0

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the upstream data source per marketplace and, crucially, that non-supported marketplaces return a possibly outdated snapshot rather than live data. It does not say what happens when the id is unknown (error vs. empty) or mention any auth or rate-limit constraints.

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 short sentences, front-loaded with the action, then the per-source behavior and the fallback caveat. Every sentence adds distinct information with no repetition of the tool name or 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?

A one-parameter lookup with an output schema and no annotations: the description covers purpose, data source, and freshness caveats, which is nearly everything needed to call it correctly. Only the not-found/failure behavior is left unstated.

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 description coverage is 100% and the single parameter already documents the expected id shape with examples. The description adds marketplace context that implicitly explains which id prefixes are live-served, but no syntax or format detail beyond the schema. Baseline 3 applies.

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 first line states a specific verb and resource with scope: 'Fetch one offer by id.' That clearly separates it from search_offers (which returns many). It stops short of naming a sibling alternative explicitly, so a 4 rather than 5.

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 gives clear context for what data you actually get per marketplace: live TMAPI/eBay Browse data for taobao/tmall/1688/jd/pdd/ebay_au, and a cached snapshot from the last search for everything else. That effectively tells an agent when the result may be stale. There is no explicit 'use X instead when...' routing or exclusion statement.

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