Skip to main content
Glama
Sign In
windy-word-mcp

windy-word-mcp

by sneakyfree
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

archives_by_date_range

Retrieve archived voice-to-text sessions filtered by a start-to-end date range, with optional limits. Sessions sorted newest first.

Instructions

Return archived sessions whose start timestamp falls within [from, to]. Either endpoint is optional — omit from for "since beginning", omit to for "until now". Sorted newest first. Use ISO 8601 (date or date+time, e.g. "2026-05-20" or "2026-05-20T18:00:00Z").

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

Input Schema

NameRequiredDescriptionDefault
toNoISO 8601 end of window. Inclusive.
fromNoISO 8601 start of window. Inclusive.
limitNoCap the returned entry count. Default 200.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses sorting order (newest first), endpoint optionality, and ISO 8601 format requirement. Missing mention of the limit parameter's default (200) and behavior when limit is omitted, though schema covers limit description.

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?

Two sentences, front-loaded with purpose. No wasted words. Essential details about optionality, sorting, and format are compactly presented.

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?

No output schema, but description adequately conveys what is returned (archived sessions) and the filtering criteria. Could mention the limit default explicitly, but overall complete for a simple list tool.

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?

Schema coverage is 100%, baseline 3. Description adds value by explaining inclusiveness of endpoints, optionality, and providing an ISO 8601 format example. This enriches the schema's parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb and resource: 'Return archived sessions' filtered by date range. However, it does not differentiate from sibling tools like 'list_archive_entries' or 'search_archives' which also list archives, missing an opportunity to clarify uniqueness.

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?

Describes when to use (when filtering by date range) with optional endpoints, but no guidance on when not to use or alternatives among siblings like 'search_archives' for more complex queries. Usage context is implied but not explicit.

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