markdown-vault-mcp

Overview Schema Source Related Servers Discussions Admin

export_area_metrics

Export area metrics as CSV or JSON over a custom date range, turning daily note metadata into trend-ready data for external analysis.

Instructions

Export area metrics as CSV or JSON for trend analysis.

Dumps daily note metadata for the area's criteria fields over a date range. Useful for plotting trends externally.

Args: area: Area name or ID (e.g. 'health', 'HEA'). format: Output format ('csv' or 'json'). from_date: Start date in YYYY-MM-DD format. Defaults to 30 days ago. to_date: End date in YYYY-MM-DD format. Defaults to today.

Returns: CSV or JSON string with daily values for each criterion field.

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": {
      "area": "<area>"
    },
    "name": "export_area_metrics"
  }
}

Input Schema

Name	Required	Default
`area`	Yes
`format`	No	csv
`to_date`	No
`from_date`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Sep 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool is an export/read operation, describes the output content, and clarifies the date-range behavior. It stops short of stating potential caveats like data volume, permission requirements, or invalid-area behavior, but the core behavior is transparent.

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 well-structured and front-loaded: the first sentence states the core purpose, followed by a short context sentence, then a clear Args section, and a Returns line. Every sentence adds useful information with no repetition of the schema.

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?

The description covers the tool's purpose, parameters, defaults, and return value, and an output schema exists to detail the return shape. It is complete for an export tool, though it does not mention edge cases or constraints such as invalid area names or very large date ranges.

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 description coverage is 0%, so the description fully compensates. Every parameter is explained: area name/ID with examples, format choices, and date format with defaults that add meaning beyond the schema's null/default values.

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 ('export'), a clear resource ('area metrics'), and the concrete output formats ('CSV or JSON'). It also defines the content as 'daily note metadata for the area's criteria fields over a date range,' which clearly distinguishes it from siblings like get_area_report or get_activity_report.

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 frames the tool for 'trend analysis' and 'plotting trends externally,' giving clear context for when it is appropriate. It does not explicitly name alternatives or exclusions, but the use case is specific enough to guide selection.

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