Skip to main content
Glama

Outil.io

Sync mailbox

sync_mailbox

Relever tout de suite la boîte mail IMAP du projet (relève automatique toutes les 2 minutes).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is partly covered; the description adds useful context that a background sync runs every 2 minutes, framing this as an on-demand trigger. However it says nothing about whether the call blocks until the sync completes, what happens if a sync is already running, whether it can fail on auth/connection problems, or what a successful result contains – and there is no output schema to cover the return side.

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?

A single short sentence with the action front-loaded ("tout de suite") and the supporting context (auto-sync cadence) placed after it. No wasted wording, though the sentence is written in French while the name, title and annotations are English, a small consistency cost for an English-speaking agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, no output schema and annotation-only safety metadata, the definition is almost complete by volume, but it leaves open the practically important questions an agent must resolve before calling: does it block, how long can it take, and does the response report newly fetched messages. Those gaps keep it at minimum-viable rather than complete.

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 no parameter meaning for the description to add; the baseline for a parameterless tool applies. Nothing in the description misrepresents the empty schema.

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?

"Relever tout de suite la boîte mail IMAP du projet" states a specific verb (relever/fetch) and resource (IMAP mailbox of the project), and the parenthetical contrasts it with the automatic 2-minute poll, so the agent understands this is a manual force-refresh. It does not name any sibling to differentiate against (e.g. sync_section), but the scope is unambiguous.

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

Usage Guidelines4/5

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

By noting that retrieval already happens automatically every 2 minutes, the definition implicitly tells the agent this tool is for triggering an immediate refresh rather than routine fetching. There is no explicit "use when / do not use when" phrasing or named alternative, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.