Skip to main content
Glama
Sign In
edhec-mcp

edhec-mcp

by Sillvs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Snack-corner offer today

resto_order_offer
Read-onlyIdempotent

Check today's EDHEC snack corner pre-order options, including available formula, in-stock products, and the same-day ordering deadline; no booking is made.

Instructions

Read-only. What you can pre-order today at the EDHEC snack corner (Click & Collect "Le Break"): the formula (1 main + sides), products still available with stock, and the ordering deadline (same day, until about 10:00 Paris time). Nothing is booked.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, and the description reinforces this with 'Read-only' and 'Nothing is booked.' It adds genuinely new behavior: a same-day ordering cutoff around 10:00 Paris time, which is nowhere in the structured data and is critical for an agent deciding whether ordering is still possible.

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?

It leads with 'Read-only,' then the resource, then the payload contents, then the deadline constraint, which is good front-loading. It is a single dense sentence with a parenthetical brand name and quoted service name that add slight clutter but also real disambiguation.

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?

No output schema exists, so the description must convey return content, and it does: the formula composition, products with stock, and the deadline. For a zero-parameter read tool this is nearly complete; only the relationship to the ordering siblings is left unstated.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies no input is required by framing the result as a fixed 'today' snapshot.

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 uses a concrete verb and resource: it tells the agent it will see what can be pre-ordered today at the EDHEC snack corner, plus the formula, available stock, and the deadline. The closing 'Nothing is booked' implicitly separates it from the ordering siblings, but no sibling is named, so the differentiation is inferential rather than explicit.

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: it is a pre-read before ordering, and 'Nothing is booked' signals that a separate commit step exists. However, it never names resto_order_prepare or resto_order_confirm, nor states the condition ('call this first, then prepare'), leaving the agent to infer the sequence from sibling names 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