Skip to main content
Glama

summarize_inbox_conversation

Read-only

Summarize a contact's recent conversation in the approved business using its Inbox AI settings.

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": {
      "id": "<id>"
    },
    "name": "summarize_inbox_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only that AI settings influence the result; it does not disclose summary length, what 'recent' means, or why idempotentHint=false despite a read-only summarize operation. Useful context but not rich.

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?

One front-loaded sentence with no filler. However, its brevity is bought at the cost of the missing details noted elsewhere, so it is efficient rather than exemplary.

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?

For a simple read-only, single-parameter tool with no output schema, the definition covers the core action but leaves out the identifier's meaning, the recency window, and the dependency on configured AI settings. Those omissions matter for correct invocation.

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?

The single parameter is named generically 'id' with 0% schema description coverage, and the description does not clarify whether it is a contact ID or a conversation ID, nor its format constraints. The phrase 'a contact's recent conversation' allows an inference of contact ID, but that is weak given the parameter's abstract name.

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 (Summarize), resource (a contact's recent conversation), and scope (within the approved business, using Inbox AI settings). An agent can tell it apart from siblings like get_inbox_ai_settings or draft_inbox_reply, though it never names an alternative directly.

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?

Usage context is implied rather than stated: 'recent conversation in the approved business' hints at scope, and 'using its Inbox AI settings' hints at a prerequisite (AI settings must be configured). There is no explicit when-to-use versus alternatives, no note on how 'recent' is bounded, and no stated failure mode when AI settings are missing.

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