Skip to main content
Glama

cloud_catalog

Read-only

Generates a greppable catalog file listing rules and one line per operation for a specified provider, so you can search API operations quickly.

Instructions

Write a greppable catalog file (rules + one line per operation) for a provider

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": {
      "provider": "<provider>"
    },
    "name": "cloud_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNotarget file
providerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior1/5

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

The description says it writes a catalog file and the schema exposes a 'path' (target file), i.e. an environment write with overwrite implications, while annotations declare readOnlyHint=true. It also does not say what happens when path is omitted or whether an existing file is clobbered.

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 compact sentence with the artifact front-loaded and no filler. It is terse rather than padded, though the terseness contributes to the behavioral ambiguity.

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?

For a file-producing tool with no output schema and only contradictory annotations, the description omits return/artifact behavior when 'path' is absent, overwrite semantics, and how 'rules' are sourced. An agent cannot confidently predict the side effects.

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 coverage is 50% and 'provider' is undocumented in the schema, but the description implies it selects which provider's rules and operations go into the catalog, and adds that content is 'rules + one line per operation'. It adds no format or syntax detail for 'path' beyond the schema's 'target file'.

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 concrete verb and artifact: it writes a greppable catalog file containing rules and one line per operation for a given provider. That is clearly distinct from the sibling verbs cloud_call, cloud_describe, cloud_search and cloud_providers, though the description never explicitly contrasts itself with them.

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 statement of when to use this tool, no prerequisites, and no pointer to an alternative when the agent only wants to query a provider rather than produce a catalog. Usage is only inferable from the phrase 'for a provider'.

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