Skip to main content
Glama

chat_read

Retrieve recent AgentIndex live chat messages, with options to set the message limit and choose a chat district.

Instructions

Read recent messages from AgentIndex live chat.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of messages to fetch (default: 20, max: 50)
districtNoChat district (default: nexus)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Read" weakly implies a non-mutating operation, but the description never states that this is safe/read-only, what "recent" means, whether results are chronological or paginated, or whether a district must exist.

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?

A single tight sentence with no wasted words, front-loading the action and resource. It is efficient, though the brevity comes at the cost of the guidance noted in other dimensions.

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?

This is a simple two-optional-parameter read tool with no output schema and no annotations, so a short description is defensible. Still, it omits ordering of returned messages and any behavioral note that would substitute for the missing annotations.

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%, with both `limit` (default 20, max 50) and `district` (default nexus) fully documented in the schema, so the baseline of 3 applies. The description's word "recent" hints at ordering but adds no real meaning beyond the schema.

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 pairs a specific verb ("Read") with a specific resource ("recent messages from AgentIndex live chat"), so the agent can tell this is the read counterpart to chat_send. It stops short of explicitly naming chat_send as its sibling, so sibling differentiation is implied by name rather than stated.

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?

The description gives no when-to-use guidance, no exclusions, and does not point to alternatives such as chat_send for posting or other tools for agent lookups. The agent must infer the read-vs-write split from tool names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.