Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Report Connector Phone Numbers Count

get_report_connector_phone_numbers_count
Read-onlyIdempotent

Retrieves the total phone number count for a given connector via the IPEX API, so you can check how many numbers a connector holds before reporting or managing them.

Instructions

Phone number count of a connector. IPEX API: GET /v1/reports/connectors/{connectorId}/phoneNumbers/count.

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": {
      "connectorId": "<connectorId>"
    },
    "name": "get_report_connector_phone_numbers_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectorIdYesPath parameter 'connectorId' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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=true, so the safety profile is fully covered without the description. The description adds only the underlying endpoint (GET /v1/reports/connectors/{connectorId}/phoneNumbers/count), which is traceability rather than agent-relevant behavior; it says nothing about what the count covers or how it is returned.

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?

Two short sentences with the purpose front-loaded and no padding. The trailing endpoint string is arguably redundant for an agent but is compact and does not obscure the main statement.

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 one-parameter read tool this is close to adequate, and the annotations carry the safety profile. However, with no output schema, the description never states the return shape (e.g. a single integer count versus an object) or the unit/scope of the count, leaving a real gap.

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?

With one parameter at 100% schema description coverage, the schema already documents connectorId as a path parameter, so the baseline of 3 applies. The description adds no extra meaning such as format, validation, or what happens with an unknown connectorId.

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 specific resource (a connector's phone numbers) and the specific operation (count), which is distinguishable from the sibling list_connector_phone_numbers. It is a noun phrase rather than a full verb+resource statement, and no sibling is named explicitly, so it stops short of a 5.

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: nothing says to call this instead of list_connector_phone_numbers when only a total is needed, and no prerequisites or context are given. Usage is only inferable from the word 'count' in the name and description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools