Skip to main content
Glama

Numbers you can call from

caller_ids
Read-onlyIdempotent

The phone numbers this organisation owns and can place calls from, with each number's status. 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": "caller_ids"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo0-based page number, default 0
perPageNoPage size, default 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description confirms read-only (redundantly) and adds that returned numbers include status, but it does not mention permissions, filtering behavior, or ordering.

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?

The description is very short and front-loaded with the primary purpose. However, the standalone 'Read only' sentence largely repeats the readOnlyHint annotation rather than adding invocation-relevant detail.

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?

This is a simple read-only listing tool with only optional pagination parameters, and the schema fully documents them. The description identifies what is returned (owned numbers with status); minor gaps around status values or return shape are acceptable given the low complexity.

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%, with page and perPage defaults documented in the schema. The description adds no pagination semantics, so the baseline score 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 states the resource (phone numbers owned by the organisation), the qualifying capability (can place calls from), and the return content (each number's status). It is clear, but it does not explicitly differentiate itself from sibling call-placement tools.

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?

Usage is implied: retrieve available caller IDs before choosing a number to call from. 'Read only' signals safe lookup, but there is no explicit when-to-use/when-not guidance or named alternative such as outbound_call for actually placing a call.

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.