Skip to main content
Glama

catalog

Read-onlyIdempotent

The caller-visible index of available tools. Three reference surfaces have distinct effects: catalog lists which tools exist; docs({ topic }) returns the static contract for one surface; advisor({ question }) can answer open-ended questions from an authorized live project's state.

catalog returns the directory / table of contents / manifest for every tool available to this caller on the active surface, grouped by category with a one-line summary per group: { categories: { project: { summary, tools: [...] }, db: { summary, tools: [...] }, ... } }. Categories cover projects, deploys, database, files, env vars, end-user auth, email (out + inbox), AI (chat + media), jobs, cron, queue, logs, errors, usage, feedback, domains, search, web scraping, push, rate limiting, telegram, analytics, captcha, payments, live updates, render, stock photos, and platform help.

For admin/operator callers the same response also includes every registered plain-English platform census question, symptom, and authority declaration. That is the discovery call before somewhere_tech_stats({ metric_id }) or debug_project({ identifier, symptom }); no table name or SQL knowledge is required.

Search: search finds a tool by keyword or exact name — e.g. catalog({ search: "auth_signup" }), catalog({ search: "upload url" }). Returns matching tools + their group + how to load each. Most tools are not in the default surface, so an empty default tool-search is not evidence that a tool is unavailable.

Lazy-load: load returns FULL tool definitions for one or more groups instead of the index — catalog({ load: "auth" }), catalog({ load: "db,fs" }), or load: "all". A group-scoped connection (?groups=db,fs on the MCP URL, or the Mcp-Tool-Groups header) limits a session to the tools it needs.

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
loadNoOptional full-definition selector for one group ('db', 'auth', …), a comma-separated list ('db,fs'), or 'all'. An omitted value returns the group index with names and summaries only.
searchNoOptional keyword or exact tool-name search across every tool available to the caller on the active surface (e.g. 'auth_signup', 'upload url', 'rollback'). The result contains matching tools, their groups, and loading details; it covers capabilities absent from default tool search.
project_idNoOptional project UUID, subdomain, slug, or 'default'. When supplied, the response also lists active runtime-fix notices for that project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description goes further by disclosing that admin/operator callers get extra census questions, symptoms, and authority declarations in the same response, and that group-scoped connections via URL query or `Mcp-Tool-Groups` header restrict the visible tool set. It does not describe pagination or size limits, but for a read-only index tool 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?

Front-loaded with the core definition and organized under bold headers for Search and Lazy-load, so it scans well. The long enumeration of ~30 categories is the one stretch that could be trimmed without losing routing information.

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

Completeness5/5

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

With no output schema, the description still supplies the response envelope, the admin-only additions, and the group-scoping behavior — everything an agent needs to call it and interpret the result. Nothing material for a zero-required-parameter read-only index tool is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above baseline by giving concrete invocation examples (`search: "auth_signup"`, `search: "upload url"`, `load: "db,fs"`, `load: "all"`) and by explaining that `load` swaps the index for full definitions rather than filtering it. `project_id`'s effect (runtime-fix notices) is only in the schema, not the description, which keeps this from a 5.

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 first sentence states the specific resource ('the caller-visible index of available tools') and the description immediately contrasts catalog with docs and advisor, so an agent can distinguish the three reference surfaces without opening any schema. It also names the return shape (`{ categories: { project: { summary, tools } } }`), which pins down what 'index' means concretely.

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

Usage Guidelines5/5

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

Explicit routing rules are given: catalog to list, `docs({ topic })` for a static contract, `advisor({ question })` for open-ended questions against live project state. It also states a non-obvious exclusion ('an empty default tool-search is not evidence that a tool is unavailable') and explains when to prefer `search` or `load` over the plain index.

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