Skip to main content
Glama

export

Generate replayable evidence and patch artifacts from a verification session, preserving verification status so prose cannot make incomplete results appear verified.

Instructions

Export independently checked evidence and patch. Prose cannot make an incomplete result verified.

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": {
      "session": "<session>"
    },
    "name": "export"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already state readOnlyHint=false and destructiveHint=false, so safety framing is partly covered, but the description adds little beyond a vague precondition. It does not say what is mutated or created, whether the export is idempotent, what happens if evidence is unverified, or whether the operation can fail on incomplete results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, so nothing is bloated, but the second sentence is an opaque aphorism that reads more like a slogan than usable instruction and is placed where the key operational detail should be. The text is front-loaded with the verb but not with actionable content.

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?

Misfiled as below because: for a single-parameter, non-destructive mutation tool with no output schema, the description should at minimum explain what the export yields and what precondition gates it, and it does neither. The only real content is an unexplained warning, leaving an agent unable to predict the result or the failure mode.

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

Parameters2/5

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

Schema description coverage is 0% for the single required 'session' parameter, so the description carries the full burden and says nothing about it — no format, no provenance requirement, no relation to the 'evidence' being exported. With only one parameter the gap is narrow, but it is entirely unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'export' is paired with the objects 'evidence and patch', so it is not a pure tautology, but neither term is defined and the description never says what an export actually produces (a file, a bundle, a returned payload) or which system it goes to. It gives no basis for distinguishing this tool from siblings like 'write', 'compare', or 'close'.

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?

The second sentence ('Prose cannot make an incomplete result verified') is a cryptic maxim that only faintly implies a precondition: the result should be checked before exporting. There is no explicit when-to-use statement, no when-not-to-use, and no named alternative such as 'check' or 'compare' that an agent could route to.

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