Skip to main content
Glama

Doxtract

Enable or disable inbox email

set_inbox_email_enabled
Idempotent

Turn mail receiving on or off for one inbox. The address does not change. Documents already in the inbox are not affected.

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": {
      "inbox_id": "<inbox_id>",
      "enabled": "<enabled>"
    },
    "name": "set_inbox_email_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYestrue to accept mail.
inbox_idYesThe inbox id returned by create_inbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (non-destructive, idempotent, closed-world), so the bar is lower; the description still adds real context by stating the address is unchanged and existing documents are unaffected. It stops short of saying what happens to mail arriving while receiving is disabled, which is the one behavior an agent would still want.

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?

Three short sentences, front-loaded with the action and followed by the two most likely worries (address stability, existing documents). Nothing is redundant or padded.

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 two-parameter toggle with full schema coverage, annotations and no output schema, the definition is nearly sufficient. The residual gap is the disabled-state behavior for inbound mail (rejected, queued, or dropped), which matters for a tool whose whole purpose is switching receiving off.

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?

Schema coverage is 100% and both parameters are documented in-schema, so baseline 3 applies. The description's "for one inbox" reinforces the inbox_id scope and "on or off" maps to the boolean, but it adds no format or edge-case detail beyond what the schema already gives.

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?

"Turn mail receiving on or off for one inbox" names a specific verb (toggle), resource (inbox mail receiving) and scope (single inbox), which cleanly separates it from update_inbox, set_inbox_webhook and get_inbox_email without the reader needing to open any schema.

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?

The intent of the tool is inferable from the description, but there is no explicit when-to-use guidance, no named alternative for changing other inbox settings, and no stated prerequisites (e.g. whether the inbox must already exist or be verified).

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.