Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Request

get_request
Read-onlyIdempotent

Retrieve IPEX order details by request ID to inspect request status and associated data.

Instructions

Order detail. IPEX API: GET /v1/requests/{requestId}.

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": {
      "requestId": "<requestId>"
    },
    "name": "get_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYesPath parameter 'requestId' 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, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds no behavior beyond the endpoint, such as error handling for unknown requestId, permission requirements, or whether data is live or cached.

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 fragments, front-loaded with the resource type followed by the API mapping. Nothing is padded, though the terseness comes at the cost of clarity rather than from disciplined editing.

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?

With no output schema, the description should at least hint at what a request record contains, and it does not. For a single-parameter read whose annotations cover safety, this is minimally adequate but leaves the agent guessing about the return shape.

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 requestId parameter is fully documented in the schema, including that it is a path parameter. The description's endpoint reference corroborates this but adds no new semantic detail. Baseline 3 is appropriate.

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?

"Order detail" plus the underlying endpoint GET /v1/requests/{requestId} identifies a single-resource fetch, but it does not clearly say what a 'request' is or how it differs from sibling lookups like get_customer or get_invoice_item. The verb is implied only through the API path rather than stated.

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 statement of when to use this tool, when not to, or which sibling to prefer. The agent must infer usage from the name and the endpoint 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