edhec-mcp

by Sillvs

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Campus card balance

resto_balance

Read-onlyIdempotent

Check campus restaurant card balance and last visit via MONEWEB / ALL La Catho; top-ups are not handled here.

Instructions

Balance of your campus restaurant card (MONEWEB / ALL La Catho) and your last visit. Top-ups are payments and are not done by this server.

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_balance"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 5, 2026

TDQS

A3.9/5.0

Behavior4/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. The description adds useful behavioral context by stating what is returned and clarifying that top-up/payment operations are not handled here, though it does not mention authentication or freshness requirements.

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?

The description is two tight sentences with the core purpose front-loaded. The second sentence adds a relevant boundary condition without unnecessary detail.

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 zero-parameter, read-only tool with rich annotations and no output schema, the description adequately states what data is returned. It could be slightly more complete by mentioning authentication or data freshness, but nothing essential is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there are no parameter semantics to explain. The baseline score of 4 applies because the description does not need to compensate for missing parameter documentation.

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 clearly identifies the resource and returned data: campus restaurant card balance and last visit, with specific systems named (MONEWEB / ALL La Catho). It distinguishes itself from broader siblings like resto_history by focusing on the last visit, though it does not explicitly direct the agent to that sibling.

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 implied by the stated purpose: check the card balance and last visit. The description also gives a useful exclusion, saying top-ups are payments and are not done by this server, but it does not explicitly say when to use resto_balance versus resto_history or other resto tools.

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