Skip to main content
Glama

export_report

Creates report.md listing every screenshot with its caption in order, providing a Markdown source for lab reports, QA evidence, or documentation.

Instructions

Write report.md in the shotlog folder: every screenshot with its caption, in order. Convert it to PDF/DOCX with any tool (e.g. pandoc).

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_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoScreenshots

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 burden. It does disclose the key side effect — a file is written into the 'shotlog folder' — but says nothing about overwrite behavior if report.md already exists, whether the tool itself produces PDF/DOCX or only the markdown, or what is returned. The conversion sentence actually creates confusion rather than resolving it.

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?

Two short sentences, front-loaded with the primary action and no filler. The only inefficiency is that the second sentence's ambiguity costs more than its brevity saves, but there is no redundant or wasted wording.

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?

For a simple one-parameter tool with no output schema or annotations, the description covers the core behavior (write an ordered markdown report of screenshots and captions). It falls short on overwrite semantics, the role of the title parameter, and clarity on whether PDF/DOCX conversion is in scope.

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?

The single parameter 'title' (default 'Screenshots') has 0% schema description coverage, and the description never mentions it. An agent cannot tell from either source whether the title becomes the document heading, the filename, or is unused metadata, so the description fails to compensate for the coverage gap.

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 first sentence names a concrete verb and artifact ('Write report.md') and specifies the content scope ('every screenshot with its caption, in order'), which distinguishes it from the read-only siblings. However, the second sentence ('Convert it to PDF/DOCX with any tool') blurs whether conversion is something this tool performs or a follow-up action the agent must take manually, leaving the tool's actual boundary ambiguous.

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?

There is no explicit when-to-use guidance and no named alternative among siblings like list_screenshots. The use case (produce a document of all screenshots) is only implicitly inferable from the description, and nothing states when this should be preferred over simply listing screenshots.

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