Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Free Units History

get_free_units_history
Read-onlyIdempotent

Retrieves free units usage history for a given year and month, optionally filtered by number, from the IPEX API to track consumption over time.

Instructions

Free units usage history. IPEX API: GET /v1/freeUnits/history.

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": {
      "year": "<year>",
      "month": "<month>"
    },
    "name": "get_free_units_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesQuery parameter 'year' of the IPEX API (required).
monthYesQuery parameter 'month' of the IPEX API (required).
numberNoQuery parameter 'number' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/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 safety is covered. The description adds only the REST endpoint mapping and says nothing about what the history contains, whether results are paginated, how far back it goes, or what unit "number" refers to — meaningful gaps for a usage-history query.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short fragments with zero wasted words and the resource front-loaded, but the brevity is under-specification rather than efficiency — nothing is explained beyond the name and route.

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?

With three parameters, two of them required, and no output schema, the description should say what the history returns and how year/month constrain it. It omits all of this, leaving an agent able to guess at invocation but not at results or semantics.

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 description coverage is 100%, so the parameters (year, month, number) are already documented structurally, and the description adds nothing beyond that. Baseline 3 applies; the description does not clarify the string format for year/month or what "number" identifies.

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 the resource ("Free units usage history") but uses a bare noun phrase with no verb, so it's unclear whether this retrieves, lists, or aggregates history. The IPEX endpoint reference confirms it's a read of free-unit consumption history, distinguishing it from the customer/call/invoice-focused siblings, but the purpose statement itself stays vague.

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 guidance on when to use this tool, no prerequisites, no mention of alternatives such as other report tools for usage or quota information. The agent must infer usage entirely from the name.

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