Skip to main content
Glama
Sign In

NeoMind

by com.neomindhub.app
OverviewDiscussionsAdmin

Read an enquiry

get_conversation
Read-only

Read the transcript of one customer enquiry, in order, by its id (from list_conversations or get_briefing). Long conversations show the most recent 60 messages, with a link to the rest.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe conversation's id (a UUID), from list_conversations or get_briefing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description goes beyond the simple 'read' action by disclosing a critical behavioral trait: long conversations are truncated to show only the most recent 60 messages, including a link to the rest.

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 two sentences are highly efficient; the first defines the core functionality, and the second immediately addresses a key functional limitation regarding message truncation.

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?

For a simple read operation, the description is highly complete, addressing what data is returned (transcript), how it is constrained (60 messages), and the source of the identifying data (preceding calls).

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?

Although the schema covers the type, the description adds semantic depth by specifying that the ID is a UUID and must be sourced from specific preceding tools (list_conversations or get_briefing).

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?

The description clearly states the purpose as reading the transcript of one customer enquiry using its ID. It distinguishes itself as a retrieval tool for specific conversation details.

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

Usage Guidelines4/5

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

It clarifies the necessary prerequisite for the ID parameter, stating it must come from either list_conversations or get_briefing, which guides the agent's workflow without listing explicit alternatives.

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

All NeoMind toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources