Skip to main content
Glama

HeyIdentity

get_catalog

Read-only

Describes the profiles (claims, URL shapes, protocol behaviors), token shape options, standard claims, limits, the current terms version and the rules agents must follow. Read it before configuring a tenant.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already declares this is a safe, non-mutating call, so the description only needs additive context. It contributes that the payload contains normative "rules agents must follow" and the current terms version, which is useful behavioral framing. It says nothing about return format, document size, or caching/staleness of the catalog, which are the remaining unknowns for a no-arg reference tool.

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 dense sentence with the subject front-loaded and the call-to-action at the end; every clause names real content the catalog exposes. The parenthetical list is compact rather than padded.

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 zero parameters and no output schema, the description carries the burden of telling the agent what comes back, and it does so by enumerating the catalog's sections plus the current terms version. The only real gap is the shape/serialization of the response and how large it is, which matters for an agent planning to read it before a configuration task.

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 (empty object, additionalProperties=false), so there is nothing for the description to disambiguate. Baseline 4 applies.

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?

A specific verb ("Describes") plus an enumerated resource: profiles, token shapes, standard claims, limits, terms version and agent rules. An agent can tell this is a reference/metadata lookup rather than a tenant-specific read. It stops short of explicitly distinguishing itself from siblings like get_configuration or get_tenant, leaving the boundary to be inferred.

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?

"Read it before configuring a tenant" gives a clear trigger condition tied to the configure-a-tenant workflow. No exclusions or named alternatives are given, so the agent must still guess whether get_configuration or set_standard_claims should be consulted first for specific sub-tasks.

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