Skip to main content
Glama
Sign In
markdown-vault-mcp

markdown-vault-mcp

by agustinvalencia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

generate_visual_report

Generate a multi-panel PNG dashboard with task status, project progress, activity timeline, and velocity charts, saved to the vault for direct embedding in markdown notes.

Instructions

Generate a visual PNG dashboard with charts and save it to the vault.

Produces a multi-panel PNG image with task status pie chart, project progress bars, activity timeline, and velocity comparison. The image is saved to assets/dashboards/ in the vault and can be embedded in notes via standard markdown image syntax.

Args: project: Scope to a specific project (ID or folder name). Omit for vault-wide dashboard.

Returns: Success message with path to the generated PNG, or error message.

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": "generate_visual_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations provided, the description takes on full disclosure. It transparently states the side effect (saving a PNG to assets/dashboards/), the output format, and the return message. It does not mention overwrite behavior or permissions, but for a generate-and-save tool this is adequate.

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 compact and front-loaded: the main purpose is in the first sentence, followed by specific output details and a structured Args/Returns section. No redundant or filler text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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, the description covers what it generates, where it saves the file, how the parameter behaves, and what the return is. Even without the explicit output schema, an agent has everything needed to invoke it correctly.

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

Parameters5/5

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

Schema coverage is 0%, so the description must explain the one parameter, and it does: 'project' is defined as an ID or folder name, and omitting it yields a vault-wide dashboard. This goes far beyond the bare anyOf string/null schema.

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 states a specific verb ('Generate') and a specific resource: a visual PNG dashboard with charts, saved to the vault. It enumerates the chart types (pie, progress bars, activity timeline, velocity comparison), which clearly distinguishes it from sibling reporting tools like get_dashboard_report or get_activity_report that presumably return data rather than an image.

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 clearly indicates the tool's use case: producing a visual PNG report that can be embedded in notes, with an optional project scope. It does not explicitly name alternative tools or state when not to use it, but the context of generating an image file is clear enough to route an agent.

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

Deploy Server

Other Tools