Skip to main content
Glama

HeyIdentity

get_configuration

Read-only

Returns one configuration of the tenant as items: clients, users, custom and standard claims, settings and endpoints.

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": {
      "configuration_id": "<configuration_id>"
    },
    "name": "get_configuration"
  }
}

Input Schema

NameRequiredDescriptionDefault
configuration_idYesThe configuration id (from create_tenant or get_tenant).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the description's main added value is disclosing what the returned configuration contains (clients, users, claims, settings, endpoints), which is genuinely useful since there is no output schema. It says nothing about pagination, result size for large tenants, or behavior when the id is unknown, leaving gaps for a potentially large aggregate read.

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?

One front-loaded sentence that identifies the resource first and then lists its contents. There is no filler, though the phrase 'as items' is slightly awkward and the list could be grouped more readably.

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

Completeness3/5

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

For a single-parameter read-only lookup with annotation coverage, the description covers purpose and returned content adequately. It still omits anything about response size, ordering, or error behavior for a tool that aggregates many sub-resources, so it is adequate rather than complete.

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 description coverage is 100% and the single parameter is documented there, including its origin (from create_tenant or get_tenant). The description adds no further meaning about the configuration_id, so the baseline of 3 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?

The description names a specific verb (returns) and resource (one configuration) and enumerates the composition of the result: clients, users, custom and standard claims, settings and endpoints. That makes it distinguishable from a plain get_tenant, though it does not explicitly contrast itself with any sibling.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as get_tenant or create_configuration. The only hint about usage lives in the schema's own parameter description (the id comes from create_tenant or get_tenant), not in the tool description.

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