Skip to main content
Glama

Read a catalog listing

get_asset
Read-only

Read one listing by id as Graunt's API gives it (GET /v1/listings/{id}). To answer a question from a listing or cite it, use fetch.

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": {
      "listing_id": "<listing_id>"
    },
    "name": "get_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idYesThe listing's id (a UUID), as search returns it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / listing_id / description
      Added value: +"The listing's id (a UUID), as search returns it."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered, and the description usefully adds that the result is the API's own representation of the record. It says nothing about failure behavior for an unknown id (404 vs empty), authentication requirements, or rate limits, which an agent calling a raw endpoint would want.

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 short sentences with no filler, and the retrieval semantics are front-loaded ahead of the alternative-tool routing. Every clause carries information an agent can act on.

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-by-id tool with no output schema, the description is close to sufficient because 'as Graunt's API gives it' signals the response is the raw API shape and refers the agent to the API for structure. The missing piece is error semantics for a bad or missing id, which is the main behavioral risk left undocumented.

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 is already documented as a UUID 'as search returns it', so the schema carries the semantics. The description's 'by id' adds nothing beyond that. Baseline 3 is correct when the schema does the work.

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 verb and resource ('Read one listing by id') and even names the underlying endpoint (GET /v1/listings/{id}), so the agent knows it is a raw passthrough rather than a synthesized answer. The only friction is vocabulary: the tool is named get_asset and the title says 'catalog listing', so the agent must reconcile 'asset' with 'listing' from the description alone.

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?

Gives an explicit routing rule: 'To answer a question from a listing or cite it, use fetch.' That names the alternative sibling and the condition that selects it. It stops short of stating the converse — when raw retrieval is the right choice (e.g., when the caller needs unprocessed fields rather than a synthesized answer) — so the agent must infer it.

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