Skip to main content
Glama

get_conversation

Retrieve a specific conversation including all messages and associated tags from the Cuti-E admin platform using its unique ID.

Instructions

Get a single conversation with its messages and tags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conversation_idYesThe conversation ID (conv_...)

Implementation Reference

  • The handler logic for "get_conversation" which executes a GET request to the Cuti-E API.
    case "get_conversation": {
      result = await apiRequest("GET", `/v1/conversations/${args.conversation_id}`);
      break;
    }
  • The tool registration and schema definition for "get_conversation".
    {
      name: "get_conversation",
      description:
        "Get a single conversation with its messages and tags.",
      inputSchema: {
        type: "object",
        properties: {
          conversation_id: {
            type: "string",
            description: "The conversation ID (conv_...)",
          },
        },
        required: ["conversation_id"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It doesn't disclose whether this is a read-only operation, what permissions are needed, potential rate limits, error conditions, or what format the returned conversation data takes. The description adds no behavioral context beyond the basic function.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the core function without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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 retrieval tool with one fully documented parameter, the description is minimally adequate. However, with no annotations and no output schema, it should ideally provide more context about return format, error handling, or permissions. The description covers the basic purpose but leaves behavioral aspects unspecified.

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 description coverage is 100%, so the schema fully documents the single required parameter. The description adds no additional parameter information beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced parameter semantics.

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 clearly states the action ('Get') and resource ('a single conversation with its messages and tags'), making the purpose understandable. It distinguishes from list_conversations by specifying retrieval of a single conversation with full details, but doesn't explicitly contrast with update_conversation or delete_conversation.

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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (like needing a conversation ID), when not to use it, or how it differs from other conversation-related tools like list_conversations or update_conversation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Stig-Johnny/cutie-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server