Skip to main content
Glama
Sign In
edhec-mcp

edhec-mcp

by Sillvs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Submit the prepared absence report

aurion_absence_submit
Destructive

Submits the exact absence report the user explicitly confirmed to Aurion's HUB Front Office; use dryRun to validate the form without uploading or submitting.

Instructions

Sends exactly the report from aurion_absence_prepare to Aurion (official request to the HUB Front Office). ONLY call this after showing the user the prepared report and getting an explicit "yes, send it" for that exact report in this conversation. Works once per confirmationId; refuses if it expired or a file changed. Use dryRun=true to fill and check the form without uploading or submitting anything.

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": {
      "confirmationId": "<confirmationId>"
    },
    "name": "aurion_absence_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoFill and verify the form only. Nothing is uploaded or submitted.
confirmationIdYesFrom aurion_absence_prepare

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare this as destructive, open-world, non-read-only, and non-idempotent. The description adds important behavioral context beyond annotations: it sends an official request to the HUB Front Office, works once per confirmationId, refuses if the confirmation expired or a file changed, and explains that dryRun fills and verifies the form without uploading or submitting.

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 three tightly written sentences with no wasted wording. The core action and safety condition are front-loaded, followed by one-time confirmation behavior and the dryRun option.

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 destructive, open-world submit tool, the description covers the essential prerequisites, confirmation requirement, one-time-use behavior, expiry/file-change refusal conditions, and dryRun mode. It does not describe the success response or returned status, which is a minor gap given there is no output schema.

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?

Schema coverage is 100%, so the schema already documents both parameters. The description still adds useful meaning by explaining that confirmationId comes from aurion_absence_prepare, can be used only once, and may be rejected if expired or if a file changed, and by clarifying dryRun as a fill-and-check-only mode with no upload or submission.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it sends exactly the report produced by aurion_absence_prepare to Aurion as an official request to the HUB Front Office. It clearly distinguishes this submit tool from the sibling prepare tool by naming the prepare tool as the source of the report.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use conditions: only after showing the user the prepared report and receiving an explicit "yes, send it" for that exact report in the current conversation. It also explains the dryRun alternative for filling and checking the form without submitting, and identifies the prerequisite confirmationId from aurion_absence_prepare.

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