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

markdown-vault-mcp

by agustinvalencia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_daily_dashboard

Retrieve today's dashboard summary from your markdown vault to view tasks and events in a single overview.

Instructions

Get the daily dashboard summary (today's tasks, events, etc).

Returns: The output of 'mdv today', summarizing the day.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4/5.0
Behavior3/5

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

No annotations are present, so the description bears the full transparency burden. It does disclose that the tool summarizes the day and returns the output of 'mdv today', which strongly implies a read-only operation. However, it doesn't explicitly state side effects, permissions, or what empty/failure behavior looks like.

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 two short sentences, front-loaded with the main purpose. The second sentence adds the concrete return source without redundancy.

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?

For a no-argument tool with an output schema, the description gives enough operational context: what it summarizes and what it returns. It is slightly incomplete only in not offering any comparison to the many sibling reporting tools.

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?

The tool has zero parameters, so the schema already fully covers parameter semantics. The description adds no parameter detail, but none is needed; baseline 4 for a no-parameter tool is appropriate.

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 starts with a specific verb and resource ('Get the daily dashboard summary') and clarifies scope with 'today's tasks, events'. The mention of 'mdv today' further pins down the exact data source, distinguishing it from broader report siblings like get_dashboard_report.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The use case is implied by 'today's tasks, events' — an agent can infer this is for a daily overview. However, there is no explicit when-to-use rule or comparison with sibling tools like get_dashboard_report or get_activity_report, so the guidance is only implied.

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