Skip to main content
Glama

Nolio

Read conversations

read_conversations
Read-only

Read the messages between a coach and athletes.

Three uses, one at a time:

  • event: the comments on one workout or race, a completed trn_…/cmp_… or a planned ptrn_…/pcmp_… handle from get_calendar. Returns each conversation hanging off it with its last 100 messages, oldest first; has_more on a conversation means older ones remain: read them with thread and starting_after set to its first message's id.

  • thread: the messages of one conversation (its handle from a previous call), newest first.

  • neither: your conversations, newest first; unread_only keeps the unread ones. limit (max 100) and starting_after (the last returned id) page through a list while has_more is true.

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

Input Schema

NameRequiredDescriptionDefault
eventNo
limitNo
threadNo
unread_onlyNo
starting_afterNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already establish readOnly/non-destructive/closed-world, and the description adds substantial behavior beyond that: result ordering differs by mode (oldest first for event, newest first for thread and default), each conversation carries its last 100 messages, has_more signals older messages remain, and the drill-down procedure is spelled out. Ordering and pagination semantics are exactly the kind of thing annotations cannot convey.

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?

Front-loaded with the mode list and structured as tight bullets, so an agent can scan to the relevant branch quickly. It is somewhat dense — the event bullet packs return shape, ordering, has_more, and the drill-down instruction into one block — but no sentence is filler.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, yet the description still conveys ordering and has_more, which aids correct paging. For a 5-parameter, zero-coverage schema with rich branching behavior, this definition covers everything an agent needs to call it correctly.

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

Parameters5/5

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

Schema coverage is 0%, so the description must carry the full burden and largely does: it defines event (a trn_…/cmp_… or ptrn_…/pcmp_… handle from get_calendar), thread (a handle from a previous call), limit with its max of 100, starting_after as the last returned id, and unread_only as keeping only unread conversations. Only the default limit value (20) is unstated, which is a minor omission against an otherwise complete mapping of all five parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ('Read the messages between a coach and athletes') and then enumerates the three distinct modes (event, thread, neither), which lets an agent distinguish exactly what each call returns. This is far more than a restatement of the name/title.

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

Usage Guidelines5/5

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

Explicitly states the modes are used 'one at a time' and gives the selection condition for each: event for comments on a workout/race, thread for one conversation from a prior handle, neither for your own conversations. It also names the sibling get_calendar as the source of event handles, giving a concrete workflow.

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