Skip to main content
Glama

update_inbox_ai_settings

Idempotent

Update Inbox AI preferences for the approved business. Supply only the preferences to change.

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

Input Schema

NameRequiredDescriptionDefault
closingNo
enabledNo
greetingNo
autoDraftNo
useServicesNo
instructionsNo
closingCustomNo
greetingCustomNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds that this is a merge/patch operation where unspecified fields are left alone, which is real value beyond the annotations, but it omits validation coupling such as custom enum values requiring the corresponding closingCustom/greetingCustom fields.

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?

Two short, front-loaded sentences with no wasted words; the action comes first and the patch instruction follows. The phrase "for the approved business" adds no actionable information and could be cut.

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

Completeness2/5

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

For an eight-parameter mutation tool with zero schema description coverage, no output schema, and interdependent enum/custom-field logic, the description is far too thin. An agent cannot tell from this text what the booleans control or how the custom greeting/closing values must pair with their enum selectors.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across eight parameters, so the schema itself explains nothing about closing, enabled, autoDraft, useServices, instructions, or the two custom-text fields. The description adds no parameter meaning whatsoever, leaving the agent to infer that "custom" enums depend on teammate fields and that maxLength limits exist.

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 states a specific verb and resource: "Update Inbox AI preferences." It clearly pairs with the get_inbox_ai_settings sibling, but it never names or contrasts that sibling explicitly, and "for the approved business" is vague scoping filler rather than useful differentiation.

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?

"Supply only the preferences to change" is a useful partial-update instruction, telling the agent to send a sparse payload rather than a full settings object. However, there is no guidance on when to use this versus related update_* settings tools, nor on prerequisites such as reading current settings first via get_inbox_ai_settings.

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.

Resources