Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Internet

get_internet
Read-onlyIdempotent

Retrieves internet service detail for a given ID via the IPEX API, so you can look up connection specifics for a customer or service record.

Instructions

Get internet service detail. IPEX API: GET /v1/internet/{id}.

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": {
      "id": "<id>"
    },
    "name": "get_internet"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter 'id' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds only the GET path, without explaining what the detail includes, authentication needs, error behavior, or rate limits; with annotations covering safety, this is minimally acceptable.

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 very short sentences, front-loaded with the operation and resource. The endpoint is relevant context and there is no filler.

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 one-parameter lookup with rich annotations, the definition is minimally complete. Because there is no output schema, it leaves the shape of 'detail' unexplained and says nothing about errors or missing IDs.

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 description's endpoint template repeats that 'id' is a path parameter. It adds no ID format, constraints, or other meaning beyond the schema.

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 ('Get') and resource ('internet service detail') and includes the endpoint path. It is distinguishable from sibling resources like get_mobile and get_connector, though it does not explicitly contrast with list_internet_types or other get_* tools.

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?

Provides no when-to-use guidance, prerequisites, or alternatives. Only the resource name implies a direct lookup for a known internet service ID.

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