Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Support

get_support
Read-onlyIdempotent

Retrieves guaranteed support details by ID from IPEX, enabling assistants to answer support-related requests with API-backed data.

Instructions

Get guaranteed support detail. IPEX API: GET /v1/support/{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_support"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter 'id' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds nothing behavioral beyond that — no note on whether a missing id errors or returns null, no permission or rate-limit context, no hint about the shape of the returned "support detail".

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, front-loaded sentences with no padding, so it is easy to scan. The word "guaranteed" carries no verifiable meaning and is the only real waste.

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?

For a one-parameter read tool with full schema coverage, complete annotations, and no output schema, very little description is required; the endpoint mapping is a reasonable supplement. The remaining gap — never saying what a support record contains — is minor given the tool's simplicity.

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% for the single id parameter, so the baseline is 3. The URL template "GET /v1/support/{id}" weakly confirms id is a path segment, but the description adds no meaning beyond the schema's own "Path parameter 'id'" text.

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

Purpose2/5

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

"Get guaranteed support detail" essentially restates the name and title; "support" is never defined as an entity (ticket? contract? SLA?), so an agent cannot tell what object is retrieved or how it differs from siblings such as get_helpdesk. The only added information is the upstream endpoint mapping.

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 when another tool (e.g. get_helpdesk) would be the better choice. The agent is left to infer everything from the name alone.

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