Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Account

get_account
Read-onlyIdempotent

Fetches IPEX provider account details by username, enabling account verification and user lookup.

Instructions

Get provider user. IPEX API: GET /v1/accounts/{username}.

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": {
      "username": "<username>"
    },
    "name": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesPath parameter 'username' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/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. The description adds the underlying API endpoint (GET /v1/accounts/{username}), which is modestly useful context, but it says nothing about what the response contains, permission requirements, or error behavior for unknown usernames.

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 with zero filler, and the core purpose is front-loaded ahead of the endpoint detail. It is efficient, though it is terse to the point of under-specifying rather than being genuinely compact-but-complete.

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 single-parameter, read-only lookup whose annotations and schema are fully populated, this is close to sufficient: the endpoint mapping plus the schema lets an agent call it correctly. Only the meaning of the returned account data is unaddressed, which is a small gap given there is no output schema.

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% with a single documented path parameter, so the baseline is 3. The description only reinforces that username is a path segment of the IPEX API; it adds no format, validation, or sourcing hints beyond the schema.

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?

The description names a specific verb and resource ("Get provider user"), which is better than nothing. However, "provider user" is vague — it does not clarify whether this returns the calling account or an arbitrary account, and against siblings like get_current_user, get_customer, or get_provider_settings an agent cannot confidently tell which to pick.

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 guidance about when to use this tool versus alternatives, no mention of prerequisites such as needing a username known in advance, and no stated exclusions. The agent must infer the applicable context entirely.

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