Skip to main content
Glama

Get an agent conversation

get_conversation
Read-onlyIdempotent

One of YOUR conversations (conversation_id from list_conversations) with its newest messages, oldest first (limit 1-200, default 100). Each message: id, role (user | assistant), content (text, plus images on user turns, stopped when the reply was cut off, case_verdict when it assessed a Gambit), searches (web sources the reply cited), follow_ups (suggested next questions), symbols, llm_route (on assistant turns: which provider/model answered, key_source user|gambit, and used_fallback + fallback_reason + notice when the user's own LLM key failed and Gambit's model answered instead) and created_at. A conversation that is not yours answers 404. After ask_gambit_agent returns status running, pass wait_for_reply_after=asked_at: the call returns as soon as the reply is saved (reply_pending false), or after wait_seconds with reply_pending true, so call it again; no need to guess a delay. (Requires api:chat.)

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": {
      "conversation_id": "<conversation_id>"
    },
    "name": "get_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
wait_secondsNowith wait_for_reply_after: the longest to wait, default 40
conversation_idYes
wait_for_reply_afterNoasked_at from an ask_gambit_agent result with status running: wait until an assistant message created after it is saved, then return at once

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / wait_for_reply_after
      Added value: +{
      +  "description": "asked_at from an ask_gambit_agent result with status running: wait until an assistant message created after it is saved, then return at once",
      +  "format": "date-time",
      +  "type": "string"
      +}
    • addedInput schema / properties / wait_seconds
      Added value: +{
      +  "description": "with wait_for_reply_after: the longest to wait, default 40",
      +  "maximum": 40,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, and the description adds real context on top: the 404 ownership rule, the api:chat permission requirement, and the long-poll return contract (reply_pending false when saved, true after wait_seconds so it must be called again). It does not discuss pagination or how to page past the limit, which is the main remaining gap.

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 identity and scope sentence, then the wait workflow, then the permission note. The middle enumeration of every message field is long but earns its place because no output schema exists; the single-paragraph packing makes it denser than ideal.

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?

With no output schema, the description supplies the return shape (id, role, content variants, searches, follow_ups, llm_route fields, created_at), the auth need, the error case, and the async wait protocol — everything required to call and interpret 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 only 50%, and the description compensates fully: limit range and default (1-200, default 100), the meaning of wait_for_reply_after as asked_at from a running ask, and that wait_seconds caps the wait with reply_pending true signaling a retry. No parameter is left to inference.

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+resource+scope: fetch one of YOUR conversations, identified by conversation_id sourced from list_conversations, returning newest messages oldest-first. The sibling relationship (list_conversations for ids, ask_gambit_agent for asking) is stated, so an agent can place it without opening schemas.

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 routes the agent: conversation_id comes from list_conversations, and after ask_gambit_agent returns status running, pass wait_for_reply_after=asked_at instead of guessing a delay. It also states the exclusion case (a conversation that is not yours answers 404).

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