Skip to main content
Glama

Outil.io

Poll outreach inbox

poll_outreach_inbox

Relire tout de suite la boîte de réception du client (réponses et rebonds), sans attendre la lecture automatique toutes les 5 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": "poll_outreach_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and openWorldHint=false, and notably readOnlyHint=false, so the agent knows this is a non-destructive but state-touching operation. The description adds genuinely useful context, the existence of a 5-minute background poll that this call bypasses, which implies a rate/frequency consideration. It does not say what side effects the forced poll has (marking messages read, cost, latency) or what comes back, leaving the readOnlyHint=false unexplained.

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?

One sentence, front-loaded with the action ('relire tout de suite') and followed by the scope (replies and bounces) and the rationale (bypass the 5-minute auto-read). No filler to cut.

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 light annotations, the description carries the burden of explaining the outcome of the forced poll, and it does not: it never says what is returned (new replies, bounce counts, whether anything is persisted) or what the readOnlyHint=false means in practice. It is adequate for triggering the call but incomplete for interpreting the result.

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 and the baseline of 4 applies. Nothing in the description misleads about 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?

States a specific verb and resource: immediately re-read the client's inbox, covering both replies and bounces. That is far more specific than the name alone and an agent can tell it apart from get_outreach_readiness or approve_outreach_messages. It stops short of naming a sibling it must not be confused with, so it is clear but not differentiated by comparison.

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?

The trigger condition is explicit: use it when you don't want to wait for the automatic 5-minute read, i.e. right after an action whose replies you need now. There are no exclusions or named alternatives, but the timing context alone is enough for an agent to decide when to call it.

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.