Skip to main content
Glama
mijneetmeter-mcp

mijneetmeter-mcp

by jhofstede

today

Read-only

Returns the current date in DD-MM-YYYY format so diary tools receive the date format they require.

Instructions

Get today's date in DD-MM-YYYY format (the format the diary tools use).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive behavior, so safety is covered; the description adds genuine value by pinning the exact return format and its downstream purpose. The one real gap is timezone: 'today' is ambiguous for a server-side clock, and that is not addressed.

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?

A single sentence with the action first and the format constraint front-loaded; every clause carries information and nothing is padded.

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 trivial read-only, parameterless tool with no output schema, the definition covers purpose, format, and integration context adequately. Only the timezone/clock source is left unstated, a minor but real ambiguity for date resolution.

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?

There are zero parameters, which is the baseline 4 case. The schema is empty and the description correctly spends no words on inputs.

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?

States a specific verb and resource ('Get today's date'), commits to an exact output format (DD-MM-YYYY), and explains why that format matters by tying it to the diary tools. An agent knows exactly what it gets back without inspecting anything else.

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 parenthetical hint that diary tools use this format implies the tool should be called before constructing date arguments elsewhere, but no explicit when-to-use or when-not guidance is given. Usage is inferable rather than stated, and no alternative for non-today dates is named.

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