Skip to main content
Glama

The internal extension directory

directory
Read-onlyIdempotent

Every dialable seat in this organisation, with presence where available — who a call could be transferred to. Pass an extension to resolve just that one. Read only.

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

Input Schema

NameRequiredDescriptionDefault
extensionNoResolve one extension instead of listing all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world, and the trailing 'Read only' largely restates readOnlyHint. What the description does add is useful: presence data may be absent ('where available'), and results are scoped to this organisation only. It says nothing about result volume or pagination for a full 'every seat' listing, which is the main operational unknown.

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 what the tool returns and who it represents, followed by the parameter behavior. No filler or repetition beyond the minor redundancy of 'Read only' against the readOnlyHint annotation.

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?

For a simple one-optional-parameter read tool with full annotation coverage and no output schema, the description covers scope, the presence caveat, and both call modes. The only meaningful gap is the shape of returned entries (name, extension, presence) and any size limits on the full listing.

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 optional 'extension' parameter is fully documented in the schema. The description only paraphrases it ('resolve just that one'), adding the nuance that the response narrows to one entry rather than filtering a list. Baseline 3 is appropriate when the schema already carries the parameter semantics.

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 the resource precisely — every dialable seat/extension in the organisation — and frames it functionally as 'who a call could be transferred to', which separates it from roster-style siblings like agent_list. The 'resolve just that one' clause covers the singleton mode. It stops short of naming an alternative outright, so it is clear but not explicitly differentiated.

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

Usage Guidelines3/5

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

It gives an implicit usage rule: call with no arguments to enumerate all seats, or pass an extension to resolve a single one. There is no explicit when-not guidance and no named alternative for related lookups (e.g. agent_list or contact_search), so the routing decision is left to inference.

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.