Skip to main content
Glama
Sign In
A2Me MCP Server

A2Me MCP Server

by Kinnectd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get upcoming family dates

get_upcoming_family_dates
Read-onlyIdempotent

Retrieve upcoming birthdays, anniversaries, and family events within a specified number of days. Get dates in month-day format to plan celebrations and stay prepared for important occasions.

Instructions

Returns upcoming birthdays, anniversaries, and family events. Dates shown as month-day only.

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_upcoming_family_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysAheadNoDays to look ahead (default: 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the behavioral detail that dates are shown as month-day only, which is useful, though not extensive.

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 short, focused sentences. The first states the core function and the second adds a relevant formatting detail. No filler or 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 simple read-only tool with one optional parameter, the description is sufficient. It explains what is returned and the date format. The absence of an output schema is mitigated by the clear return description, though more detail about event types could be added.

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

Parameters3/5

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

The schema covers the only parameter (daysAhead) with a full description and default value. The tool description adds nothing beyond the schema, so it meets the baseline for high schema coverage.

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 clearly states the tool returns upcoming birthdays, anniversaries, and family events, using a specific verb and resource. This distinguishes it from siblings like get_upcoming_events by specifying the family-related scope.

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 purpose is implied well enough, but no explicit guidance is given on when to use this tool versus alternatives like get_upcoming_events or answer_family_date_question. The description does not mention exclusions or alternative tools.

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