Skip to main content
Glama

list_inbox

Read-onlyIdempotent

List your private item, Support and Wanted chats. Filters: all, buying, selling, archived, wanted, support. Your canonical Support entry stays last.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
filterNo
max_feeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / filter / enum
      Previous value: -[
      -  "all",
      -  "buying",
      -  "selling",
      -  "wanted",
      -  "support"
      -]New value: +[
      +  "all",
      +  "buying",
      +  "selling",
      +  "archived",
      +  "wanted",
      +  "support"
      +]
  2. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two genuinely new traits: the result set covers only private/Support/Wanted chats, and the canonical Support entry is pinned last. It stops short of describing pagination behavior, ordering of the remaining entries, or what a 'canonical' Support entry means.

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?

Three short sentences, front-loaded with the resource, followed by filters and then the ordering guarantee. The filter enumeration duplicates the schema enum, which is the only wasted text.

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 a four-parameter, paginated list tool with no output schema and no parameter documentation, the description omits pagination mechanics (limit/cursor) and entirely ignores max_fee. An agent could invoke it, but not confidently for filtered or paged use.

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 four parameters, so the description must carry the burden. It only re-lists the filter enum values already present in the schema and says nothing about limit, cursor, or the cryptic max_fee string parameter, which an agent could easily misuse.

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 uses a specific verb (list) plus resource (chats) and scopes it to 'private item, Support and Wanted chats', so the agent knows exactly what surface is returned. It does not contrast with siblings such as read_thread, but the purpose itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus read_thread or browse, and no prerequisites or exclusions. Usage is only implied by the word 'List', leaving the agent to infer that this is the entry point for scanning conversations.

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