Skip to main content
Glama
Sign In
selfos-mcp

selfos-mcp

by AmineBenaceur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

upcoming_birthdays

Read-only

Retrieve birthdays occurring within a specified number of days to plan reminders and messages. Set the window in days, defaulting to 30, and get upcoming dates from your vault.

Instructions

Birthdays in the next N days.

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

Input Schema

NameRequiredDescriptionDefault
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without description help. The description adds nothing beyond that -- no indication of what fields are returned, whether results are sorted, how the date window is computed (inclusive/exclusive, timezone), or what happens when no birthdays fall in range.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and wastes no words, but it errs toward under-specification rather than conciseness -- there is room for one more sentence of behavioral detail at negligible cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple one-parameter read tool with annotations and no output schema, so the bar is low, yet the description still leaves the return shape (names? dates? ages?), ordering, and data source unstated. For a tool an agent will surface directly to a user, that is a meaningful gap.

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?

Schema coverage is 0% and the sole parameter 'days' is undocumented in the schema, but the phrase 'next N days' does establish that it is a forward-looking window rather than a backward one, and the default of 30 is visible in the schema. It still omits units/bounds and whether the window starts today.

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?

The description names a specific resource (birthdays) and a time-bound scope (the next N days), so an agent knows exactly what it returns. It lacks a verb and any sibling comparison, but no sibling in the list overlaps with birthday lookup, so differentiation is not needed.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives, nor of prerequisites (e.g., that birthday data must exist in the vault). The agent must infer usage entirely from the one-line summary.

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