Skip to main content
Glama

Doxtract

Rename inbox or change its icon

update_inbox
Idempotent

Change an inbox's name and/or icon. Send name, icon, or both. Send icon as null to go back to the default icon. Renaming does not change the email address.

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>"
    },
    "name": "update_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoA Lucide icon name, such as "file-text" or "receipt". Send null to go back to the default. Shown on the inbox card.
nameNoThe new name. Unique in the workspace.
inbox_idYesThe inbox id returned by create_inbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description still adds non-obvious behavior: that icon=null resets to the default and that a rename leaves the email address untouched, both of which prevent agent mistakes. Return shape and name-conflict behavior are not disclosed, keeping it at 4.

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?

Four short sentences, front-loaded with the action, then the optionality rule, the null-reset rule, and the clarifying non-effect. Every sentence carries information and there is no filler.

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 three-parameter, non-destructive, idempotent update with full schema coverage and no output schema, the description covers the action, optionality, null handling and a key side-effect caveat. Only failure modes (e.g. duplicate workspace name) are unaddressed.

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 description coverage is 100%, so 3 is the floor, but the description adds real meaning the schema does not encode: that name and icon are individually optional yet at least one should accompany the required inbox_id, plus the null-reset semantics for icon. This goes beyond just restating parameter docs.

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 gives a specific verb and resource ("Change an inbox's name and/or icon") and even clarifies what it does NOT affect ("Renaming does not change the email address"), implicitly steering away from the sibling email/webhook setters. It stops short of naming any sibling explicitly, so it lands at 4 rather than 5.

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?

"Send name, icon, or both" and "Send icon as null to go back to the default icon" give concrete call patterns an agent can act on. There are no exclusions or named alternatives, but the usage context is unambiguous for a narrowly scoped update tool.

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.