Skip to main content
Glama

Outil.io

Get mailbox provisioning

get_mailbox_provisioning
Read-only

État de la création automatique de la boîte de prospection (étape, message, prochain essai) et accès manquants côté Outil.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuine behavioral value absent from structured fields: it discloses the returned content (current step, message, next attempt) and that missing accesses are reported, which matters because no output schema exists.

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 dense sentence with the resource stated first and the returned fields in parentheses. Nothing is wasted, though the trailing clause 'et accès manquants côté Outil' is grammatically loose and slightly hard to parse.

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 a read-only annotation the tool is easy to invoke, and the description does sketch the return payload. However, 'accès manquants côté Outil' is ambiguous — it is unclear whether this reports a boolean, a list, or an error state — and there is no hint about what step values look like or whether results change over time.

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 semantics to explain; the schema is complete at 100% coverage with an empty properties object. Baseline of 4 applies since nothing in the description is required to clarify inputs.

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 names a specific resource — the state of the automatic prospecting-mailbox creation — and enumerates what it reports (step, message, next attempt, missing accesses). This distinguishes it from the mutating sibling provision_prospecting_mailbox, though the distinction is implied by 'État' rather than stated explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus provision_prospecting_mailbox or sync_mailbox, no mention of polling after a provisioning attempt, and no prerequisites or exclusions. The agent must infer the read-vs-trigger relationship from the names alone.

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.