edhec-mcp

Overview Schema Source Related Servers Discussions Admin

Download school certificate

aurion_certificate

Download an official school attendance certificate as a PDF and save it directly to a chosen local folder for administrative use.

Instructions

Download your official school attendance certificate ("certificat de scolarité") as a PDF into a local folder.

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": {
      "destDir": "<destDir>"
    },
    "name": "aurion_certificate"
  }
}

Input Schema

Name	Required	Description	Default
`destDir`	Yes	Absolute local folder, e.g. ~/Documents/EDHEC/Admin

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 readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, and the description is consistent with them by making clear it writes a file into a local folder. It adds the valuable detail that the artifact is a PDF, but does not say whether an existing file at that path is overwritten (relevant given idempotentHint=false), how the filename is chosen, or whether a login session is required.

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?

A single front-loaded sentence with no filler; the key facts (certificate, PDF, local folder) all appear immediately, plus the French alias which is genuinely useful for matching user phrasing.

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 one-parameter download tool with full schema coverage and annotations covering the safety/world profile, the description is nearly complete. The only meaningful omissions are authentication prerequisites and file-naming/overwrite behavior, which matter given the openWorldHint and idempotentHint=false annotations.

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?

There is a single parameter with 100% schema description coverage, including an example path, so the schema already carries the semantics and the baseline is 3. The description's phrase 'into a local folder' confirms what destDir means but adds nothing about naming, overwrite behavior, or whether the directory must exist.

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 (download), a specific resource (official school attendance certificate / "certificat de scolarité") and the output form (PDF into a local folder). The resource is distinct from the other aurion_* siblings (timetable, view, absence), though the description does not explicitly name or contrast those siblings.

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 infer it should be called when the user wants their certificate. There is no explicit statement of when to use it, no prerequisites (e.g. prior edhec_login authentication), and no mention of alternatives or failure paths, though no direct sibling covers the same task.

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