Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Current User

get_current_user
Read-onlyIdempotent

Retrieves the authenticated IPEX user's account details, helping assistants identify the current user and access their profile context.

Instructions

Get the authenticated user. IPEX API: GET /v1/users/me.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_current_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoQuery parameter 'detail' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds the underlying endpoint mapping (GET /v1/users/me), which hints at authentication requirements and a parameter-less identity lookup, but says nothing about the shape of the result or failure modes.

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 short sentences with zero filler; the purpose is front-loaded and the API endpoint mapping follows as compact supporting context.

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 identity lookup with full annotation coverage and no output schema, the description covers what the tool does and which endpoint backs it. It could note the authentication requirement or typical returned fields, but nothing critical for correct invocation is missing.

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 optional 'detail' parameter, so the schema already documents the input. The description adds no additional meaning about what 'detail' does or how it changes the response, so the baseline 3 applies.

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?

The description states a concrete verb and resource in 'Get the authenticated user', which distinguishes it from customer/account-focused siblings such as get_customer and get_account. It doesn't name a sibling explicitly, so it sits at a clear 4 rather than 5.

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 alternative to pick when the target user is not the authenticated caller. The only hint is the phrase 'authenticated user', which implies identity context but provides no routing guidance.

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