Skip to main content
Glama

export_consultation

Export a consultation as a shareable report in markdown, JSON, or text to document decision-making, share with your team, or create ADRs.

Instructions

Export a single consultation as shareable report.

Perfect for sharing specific decision-making discussions with your team, documenting why you chose a particular approach, or creating ADRs.

Args: consultation_id: Consultation ID (e.g., "consult_1") session_id: Session identifier project_root: Absolute path to project root format: Output format ("markdown", "json", "text")

Returns: Formatted consultation report

Examples: # Export as markdown export_consultation( consultation_id="consult_5", session_id="my-project" )

# Export as JSON for CI/CD
export_consultation(
    consultation_id="consult_5",
    format="json"
)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNomarkdown
session_idNodefault
project_rootNo
consultation_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the return type ('Formatted consultation report') and provides examples, but does not explicitly state whether the operation is read-only, if it writes files, or any permission requirements. This is a moderate level of transparency.

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 well-structured with an intro, use cases, Args, Returns, and Examples. Each section is concise and adds value, with no redundant text. The examples are particularly helpful.

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?

Given the tool's moderate complexity (4 params, output schema exists), the description covers purpose, usage, parameters, and return type. It could be more explicit about the relationship between project_root and file output, and explicitly mention export_session_summary as an alternative for session-level exports, but overall it is fairly complete.

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

Parameters4/5

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

The input schema has no parameter descriptions (0% coverage), so the description's Args list provides essential meaning. It explains each parameter (e.g., consultation_id with example, format with allowed values) and examples illustrate typical usage, though it could go deeper on optionality or constraints.

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 tool exports a single consultation as a shareable report, using the specific verb 'export' and resource 'single consultation'. This distinguishes it from sibling tools like export_session_summary, which likely exports session-level data.

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?

The description provides clear use cases (sharing decision-making discussions, documenting rationale, creating ADRs) and implies the distinction from session-level exports. However, it does not explicitly mention when not to use this tool or name alternatives like export_session_summary.

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/amarodeabreu/sensei-mcp'

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