Skip to main content
Glama

export_decisions

Read-onlyIdempotent

Export decisions to JSONL or Markdown for audit, sharing, and LLM digestion. Supports filtering by project, service, type, and branch.

Instructions

Export decisions to JSONL or Markdown. Read-only; no schema mutations. Use for audit, sharing with external tooling, or pre-LLM digestion. JSONL emits one decision per line with tags parsed from the on-disk JSON column into a real array. Markdown groups by type (and by service when multi-service). Hard-capped at 5000 rows per call as a cost guard. Returns JSON: { format, content, count, scope }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_rootYesProject root to filter by (default: server projectRoot).
service_nameNoFilter by subproject name (e.g., "auth-api").
typeNoFilter by decision type.
git_branchNoBranch filter. "all" → every branch (default); any other value → that branch + branch-agnostic rows.
include_invalidatedNoInclude invalidated decisions (default: false).
formatNoOutput format (default: jsonl).jsonl
limitNoMax rows to export (default: 500, hard max: 5000).
Behavior5/5

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

Description adds significant behavioral context beyond annotations: read-only guarantee, hard cap at 5000 rows, format-specific behaviors (JSONL parsing tags, Markdown grouping), and return shape. No contradiction with annotations.

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?

Five sentences, each adding distinct value: purpose, read-only, use cases, format details, cap, and return structure. No redundancy; front-loaded with primary action.

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?

Covers key aspects: purpose, safety, parameters, output format, and limits. Lacks error conditions or permission details, but annotations fill in safety profile. Adequate for tool selection and invocation given 7 parameters and no output schema.

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?

Schema coverage is 100%, but the description adds extra semantics: default for project_root, behavior of git_branch with 'all', default format, and limit cap. This provides context beyond the schema descriptions.

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 identifies the tool as exporting decisions to JSONL or Markdown. It specifies the action (export) and resource (decisions), distinguishing it from sibling tools like 'query_decisions' or 'add_decision' by emphasizing read-only behavior and no schema mutations.

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 explicitly states use cases: audit, sharing with external tooling, or pre-LLM digestion. It contrasts the two output formats but lacks explicit guidance on when not to use this tool compared to alternatives like 'query_decisions' for in-context retrieval.

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/nikolai-vysotskyi/trace-mcp'

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