Skip to main content
Glama

Read a catalog resource

read_catalog_resource
Read-onlyIdempotent

Read one verified catalog resource by id: the extracts and the URL of their source.

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": {
      "id": "<id>"
    },
    "name": "read_catalog_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesResource id from search_catalog.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine context beyond that by disclosing the returned payload (extracts plus the source URL), which matters because there is no output schema; it does not cover error behavior for a bad id, but that is a minor gap.

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?

One tight sentence with the action and the return contents front-loaded; nothing is wasted. It is slightly compressed to the point that the phrase "the extracts and the URL of their source" takes a moment to parse.

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 simple single-parameter read with no output schema, the description supplies the essential missing piece: what the call returns. It would be complete with a brief note on what happens when the id is unknown or the resource is absent, but nothing critical to invocation 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?

There is a single parameter at 100% schema coverage, and the schema already documents the 24-hex-character id pattern and its origin. The description restates "by id" without adding format, validation, or lookup semantics beyond what the schema provides, 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?

States a specific verb and resource ("read one verified catalog resource") plus the lookup key ("by id"), which contrasts naturally with the sibling search_catalog that returns many. The description also says what comes back (extracts and source URL), so an agent knows exactly what operation this is.

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

Usage Guidelines3/5

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

The schema note "Resource id from search_catalog" implies the intended two-step workflow: search first, then read by id. However, the description itself never states when to use this versus search_catalog or request_resource, and gives no exclusions or prerequisites beyond the id's provenance.

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.