Skip to main content
Glama

get_catalog_status

Check the current status of a catalog batch and retrieve its settled results using the batch ID.

Instructions

Read current catalog status and settled results.

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": {
      "batch_id": "<batch_id>"
    },
    "name": "get_catalog_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
batch_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: no statement about side effects, permissions, or whether the read is idempotent. The ambiguous phrase "settled results" raises an unanswered question — is the tool polled until a batch settles, and does the response change over time? Nothing is said about cost, rate limits, or error behavior for an unknown batch_id.

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 short sentence with no filler and the read semantics front-loaded. It is efficient, though the brevity is partly under-specification rather than tight writing.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and an undocumented parameter, the description needed to do substantial work and instead does almost none. Nothing is said about the shape of the returned status or results, which is exactly the information an agent needs when no output schema exists to fall back on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single required parameter, batch_id, is never mentioned in the description. The agent gets no hint about where a batch_id comes from, what format it takes, or what happens if it refers to an unsettled batch. With one undocumented parameter and no compensating prose, this sits below the baseline for zero-parameter tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ("Read") and two resources ("catalog status" and "settled results"), so the agent knows this is a read of status information. However, it never clarifies what a "catalog" is in this domain, and it does nothing to distinguish itself from the sibling enrich_catalog. A reader can guess the purpose but cannot confidently rule out overlap with siblings.

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 guidance on when to call this versus alternatives, no prerequisites (e.g. that a batch must already exist), and no mention of when not to use it. The word "settled" hints at a post-processing stage but the agent must infer that lifecycle condition entirely on its own.

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