Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Customer

get_customer
Read-onlyIdempotent

Retrieves detailed information for a specific IPEX customer by ID, letting you look up customer records and account data through the IPEX API.

Instructions

Customer detail. IPEX API: GET /v1/customers/{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_customer"
  }
}

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.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond the raw endpoint string — no note on not-found behavior, required auth/tenant scoping, or what a 'detail' payload contains.

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 purpose and followed by the upstream endpoint. Nothing is wasted, though the telegraphic style borders on under-specification.

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 single-record read with a fully documented 1-param schema and no output schema, minimal description is defensible. Still, it omits what 'detail' returns and error/empty-case behavior, which an agent calling this cold would benefit from.

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 explains 'id' as the path parameter of the IPEX API. The description adds no further meaning such as id format, whether it's a customer UUID vs external id, or how invalid ids behave, so baseline 3 applies.

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?

"Customer detail" plus the endpoint mapping gives a verb-implying resource (fetch a single customer by id), but it is terse and does not distinguish this from siblings like get_customer_name or the customer report tools. An agent can guess it returns one customer record, but the description doesn't say so explicitly.

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 mention of when to prefer get_customer_name or the report siblings, and no prerequisites stated. The only routing hint is the implicit single-resource-by-id shape of the endpoint.

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