Skip to main content
Glama

get_catalog_item

Read-only

Read original sources, setup links, rating summary, and recent reports and discussions for one item.

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": {
      "item_id": "<item_id>"
    },
    "name": "get_catalog_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNocard omits feedback threads; full includes recent reports and discussions.
item_idYes
versionNo

Output Schema

NameRequiredDescriptionDefault
itemYes
topicsNo
reportsNo
contributionYes
feedback_templateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already state readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered without the description. The description adds useful content disclosure (what fields are read), but says nothing about permissions, rate limits, or pagination. There is a mild tension in that it advertises "recent reports and discussions" while the schema notes the card view omits those threads, though this is not a contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the enumerated payload is easy to scan. Its brevity is close to the right size, though it could have spent one more clause on the view/version parameters instead of only content listing.

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?

An output schema exists, so return-value explanation is not required, and annotations cover the safety profile. The remaining gap is the undocumented version parameter, which an agent would have to guess at. For a 3-parameter read tool this is largely complete but not fully.

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 only 33%: view is documented in the schema, but item_id and version have no descriptive text. The description indirectly clarifies the view distinction by listing the extra feedback content that only the full view returns, but it never explains what version means or how item_id is resolved. It partially compensates but does not close the gap.

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 description uses a specific verb ("Read") plus a bounded resource ("for one item") and enumerates the content returned: original sources, setup links, rating summary, and recent reports/discussions. That is enough for an agent to distinguish single-item retrieval from catalog browsing. It stops short of naming any sibling (e.g., get_entry) as the alternative, so it does not fully differentiate.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The phrase "for one item" implies the single-record use case versus a search, but the agent must infer that itself. No prerequisites or exclusions are stated.

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