edhec-mcp

Overview Schema Source Related Servers Discussions Admin

Campus card history

resto_history

Read-onlyIdempotent

Retrieve recent campus card purchases and top-ups, including dates, amounts, and balance changes, to review spending history.

Instructions

Recent purchases with your campus card (date, amount, balance before/after) and top-ups.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Default 30

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds the shape of the payload (transaction entries with before/after balances), which is genuinely useful, but says nothing about how far back 'recent' reaches or what happens when limit is omitted or exceeded.

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?

One sentence, front-loaded with the resource and immediately followed by the returned fields. Nothing is padded and nothing needs reordering.

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?

With no output schema, the description carries the burden of describing return values and does so at a useful level of detail. It falls just short of fully complete because the meaning of 'recent' — time window or ordering — and any indication of volume are left unspecified.

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?

The single parameter, limit, is fully documented in the schema including its default of 30 and the 1–200 bounds. The description's word 'recent' gestures at the cap but adds no ordering, time-window, or format detail beyond the schema; baseline 3 applies at 100% schema coverage.

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?

Specific verb+resource: it returns recent campus-card purchases and top-ups, and the parenthetical enumerates the returned fields (date, amount, balance before/after). It implicitly separates itself from resto_balance, but never names the sibling that returns the current balance, so differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied — an agent can guess this is for reviewing past transactions versus resto_balance for the current balance, but the description states no explicit when-to-use, when-not, or alternative. A single clause like 'for current balance use resto_balance' would have closed the gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.