Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Sms Integration

get_sms_integration
Read-onlyIdempotent

Fetch SMS service details by serviceId from the IPEX API to inspect a specific SMS integration.

Instructions

Get SMS service detail. IPEX API: GET /v1/sms/integration/{serviceId}.

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": {
      "serviceId": "<serviceId>"
    },
    "name": "get_sms_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceIdYesPath parameter 'serviceId' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond restating the HTTP endpoint — no note on permissions, failure modes (unknown serviceId), or what the returned detail object covers.

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, purpose first and endpoint second, with no filler. The terseness is appropriate for a single-parameter read, though the endpoint repetition is borderline redundant with the schema's path-parameter description.

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?

The tool is simple and safely annotated, so not much is required, but with no output schema the description is the only place an agent could learn what 'SMS service detail' actually returns, and it says nothing about that. Minimum viable for invocation, thin for interpretation of results.

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 coverage is 100% and the single parameter is documented as the 'serviceId' path parameter, so the description has little room to add meaning. It does confirm the ID is a path segment via the endpoint template, which mildly reinforces the schema, but offers no format hints (numeric vs UUID) beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb and resource ('Get SMS service detail') and pins it to the IPEX endpoint GET /v1/sms/integration/{serviceId}. However, 'SMS service detail' is left unelaborated — an agent cannot tell whether 'integration' means SMS gateway configuration, credentials, routing, or message history — and no sibling (e.g. get_mobile, get_connector) is named as a contrast.

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 alternative tools for adjacent lookups. The agent is left to infer that this is the right call whenever an SMS service ID is at hand.

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