Skip to main content
Glama

Service catalog for requests

request_catalog_get
Read-onlyIdempotent

What you can request: the 5 categories and 14 service families (English names). Pass family to get its services (slug and title) and the extra detail fields accepted by request_create.

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": "request_catalog_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
familyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is added context, which it delivers: it names the fixed catalog size (5/14), states names are in English, and discloses the return shape per family (slug, title, and the extra detail fields accepted by request_create). That cross-tool linkage is genuinely useful information not present in the annotations or schema. It does not mention whether the catalog is static or cached, a minor omission.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the no-argument result and followed by the conditional drill-down behavior. No filler, no restatement of the title, and the request_create cross-reference is packed into the same clause rather than a separate sentence.

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?

With no output schema, the description must carry the return-value burden, and it largely does: it explains the catalog counts and the per-family payload (slug, title, extra detail fields). What is left vague is the exact grouping of the no-argument response (how categories relate to families) and whether all 14 families are always returned, which an agent may need to parse the result confidently.

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 single 'family' parameter has 0% schema description coverage, but the description supplies the meaning the schema omits: the 14 families are the allowed values, they are English-named, and supplying one switches the response to that family's services plus the detail fields. The enum itself is visible in the schema, but the behavioral effect of the parameter is only explained in prose, which is exactly the compensation needed here.

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?

The description concretely states the resource returned (5 categories and 14 service families, then per-family services with slug and title) and the optional drill-down via 'family'. It is clearly a read-only catalog lookup and is distinguishable from request_create (which consumes the same detail fields) and get_service. It lacks an explicit verb, but the content is specific enough that an agent knows exactly what the tool yields.

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?

'Pass family to get its services ... and the extra detail fields accepted by request_create' gives clear conditional usage: omit family for the catalog overview, supply family for a drill-down, and do so before calling request_create. There is no explicit statement of when not to use it (e.g. versus get_service, which presumably fetches a single service), so it stops short of full routing guidance.

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