Skip to main content
Glama

Export Context Markdown

export_context_markdown

Export project context as a Markdown document so other LLMs and AI tools can share the same project background.

Instructions

Export the project context as a Markdown document for sharing with other LLMs and AI tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_context_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it. It never says whether the document is written to disk in the project root, returned inline, or if it overwrites an existing file, so the side-effect profile of a tool called 'export' is left ambiguous.

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?

One tight sentence, front-loaded with the verb and the output format, with no filler. It is arguably too short rather than padded, but structurally clean.

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?

An output schema exists, so return values need no description, and the single optional parameter is fully covered. The remaining gap is whether the export writes a file and where, which a zero-annotation tool should still state.

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 coverage is 100% and the single 'path' parameter is documented in-schema as the project root directory, so the baseline of 3 applies. The description adds nothing about how path influences scope or output location.

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 gives a specific verb+resource+format: 'Export the project context as a Markdown document.' An agent can tell this is a context-serialization tool, distinct from read_file or generate_handoff, though it never names the closest siblings explicitly.

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?

It states a rationale ('for sharing with other LLMs and AI tools') but gives no when-to-use conditions, no prerequisites, and no discrimination against nearby tools such as generate_project_brain, generate_handoff, or get_context. The agent must infer selection from the name alone.

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