Skip to main content
Glama

Catalogue (free)

catalog

FREE, no payment needed. Lists all 78 tools with a real example of the input and of the output each one returns, plus what a call costs and how to pay for it. Call this first if a tool asks for payment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations present, the description carries the burden and does disclose the important traits: the call is free, no payment is required, and it can be used as a fallback whenever another tool demands payment. It does not explicitly say the call is read-only and side-effect free, but a zero-parameter listing tool makes that near-implicit.

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?

Three short sentences, front-loaded with the most decision-relevant fact (it is free) and ending with the actionable trigger. 'FREE' and 'no payment needed' are mildly redundant, but the emphasis is defensible for a tool whose main risk is an agent assuming a paywall.

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?

There is no output schema, but the description compensates by enumerating what comes back: examples of input and output per tool, costs, and payment instructions. For a trivial zero-parameter discovery tool, that is enough for an agent to decide to call it and to interpret the response.

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

Parameters4/5

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

The tool takes no parameters, which is the baseline-4 case. The description correctly adds no parameter detail and instead spends its words on return content, which is the right allocation for a zero-argument tool.

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?

The description names a specific verb and resource: it 'lists all 78 tools with a real example of the input and of the output each one returns.' It also states the two extra payloads (per-call cost and payment instructions), which clearly separates it from every sibling tool in the list.

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?

The trigger condition is explicit: 'Call this first if a tool asks for payment,' and the lead phrase 'FREE, no payment needed' implies the meta/discovery role. It does not contrast itself with the nearest discovery-flavored sibling (x402_recommend) or say when the catalogue is unnecessary, so it falls short of a full when/when-not statement.

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