Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Check Ticketing User

check_ticketing_user
Read-onlyIdempotent

Retrieve a requestor user by username to verify identity or ticketing access before processing a request.

Instructions

Get requestor user by username. IPEX API: GET /v1/ticketing/check-user.

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": "check_ticketing_user"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds only the endpoint mapping, saying nothing about authentication requirements, what a 'requestor user' object contains, or what happens when the username is unknown. Adequate but thin beyond annotations.

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, front-loaded with the purpose and followed by the API route. The endpoint reference is marginally useful metadata rather than wasted text, though it could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A zero-parameter tool with no output schema should explain what the returned user object represents and how the username is supplied, and it does neither. For a tool whose only input appears to come from implicit context, the definition leaves the calling convention unresolved.

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 zero parameters the baseline would be 4, but the description explicitly says the lookup is 'by username' while the schema declares no username property, creating a real ambiguity about where that value comes from (path, auth context, or query). That mismatch costs a point even though there are no parameters to document.

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?

States a specific verb and resource ('Get requestor user') and adds the backing API route (GET /v1/ticketing/check-user), which clearly distinguishes it from generic user tools like get_current_user. The phrase 'by username' is precise but problematic since no username input exists, leaving the exact lookup key slightly unclear.

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?

No indication of when to use this versus get_current_user or the other get_* lookups, and no prerequisites or preconditions are stated. The agent must infer usage 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