Convocore

export_conversation

Read-onlyIdempotent

Export a single conversation. Requires a paid workspace (hasEverPaid === true); billed against monthly export quota.

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": {
      "agentId": "<agentId>",
      "convoId": "<convoId>"
    },
    "name": "export_conversation"
  }
}

Input Schema

Name	Required	Description
`format`	No	Export format (default: json)
`agentId`	Yes	The agent ID
`convoId`	Yes	The conversation ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this as a safe, idempotent read operation. The description adds important behavioral context beyond annotations: it requires a paid workspace and is billed against a monthly export quota. It does not describe the return shape, but the annotations carry the safety profile.

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?

Two sentences with no waste. The core action is stated first, followed by the prerequisite and billing constraint. Every sentence earns its place.

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

Completeness4/5

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

For a simple read-only export tool, the description covers purpose, prerequisite, and billing. The schema covers parameters, and annotations cover safety. It could say more about the returned artifact (e.g., download link vs. inline content), but no output schema exists and the essential call criteria are present.

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 all three parameters are documented by the schema itself. The description adds no parameter-level detail beyond implying that convoId identifies the single conversation; the format parameter is not mentioned. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource: 'Export a single conversation.' The word 'single' distinguishes it from the sibling export_all_conversations without requiring the agent to open either schema.

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 gives clear usage context by specifying the paid-workspace prerequisite (hasEverPaid === true) and quota billing. It does not explicitly name alternatives or when-not-to-use cases, but the 'single conversation' scope implies the boundary with bulk export siblings.

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

All Convocore tools Inspect

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

Need Help?