Skip to main content
Glama

Export numbers

export_numbers
Read-onlyIdempotent

Your numbers as CSV text.

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

Input Schema

NameRequiredDescriptionDefault
qNoMatches digits of the number or its label
tagNoOnly numbers with this tag
modeNotest for sandbox numbers, live for real ones
poolNoPool id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / mode / description
      Added value: +"test for sandbox numbers, live for real ones"
    • addedInput schema / properties / pool / description
      Added value: +"Pool id"
    • addedInput schema / properties / q / description
      Added value: +"Matches digits of the number or its label"
    • addedInput schema / properties / tag / description
      Added value: +"Only numbers with this tag"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful return-format context ('as CSV text') but does not mention export limits, whether filters narrow the output, or how large exports behave.

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 a single short sentence with no wasted words and the core action is front-loaded. Its brevity is efficient, though it leaves out usage context rather than being overly verbose.

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 simple export tool with full schema coverage and rich annotations, the description is minimally adequate. It discloses the CSV output format, but it omits usage guidance and does not explain how filters affect the export, leaving some context gaps for an agent selecting among sibling export and list tools.

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 all four parameters (q, tag, mode, pool) documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline score of 3 is appropriate.

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?

States a specific verb (export) and resource (numbers) plus the output format (CSV text), so an agent can tell it produces a CSV export rather than a JSON list. However, it does not distinguish it from close siblings like export_csv or export_consent, leaving some ambiguity about which export tool to choose.

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?

The description gives no explicit when-to-use guidance, prerequisites, or alternatives. It implies usage through the verb 'export', but an agent must infer whether to use this instead of list_numbers, export_csv, or search_available_numbers.

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.