Skip to main content
Glama
Sign In

Open Archives

by io.github.coret
OverviewDiscussionsAdmin

Births N Years Ago

get_births_years_ago
Read-only

List births that occurred a specified number of years ago

Returns a list of birth records for people born exactly the specified number of years ago from today. Note: version 1.1 uses archive_code instead of archive and includes the archive name and record URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "years": "<years>"
    },
    "name": "get_births_years_ago"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsYes
number_showNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds value by disclosing the version 1.1 change (archive_code replacing archive) and that results include archive name and record URL, which are behavioral details beyond the annotations.

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 front-loaded sentences with no fluff. The first states the core action, and the second provides return details and a version note. Every sentence earns its place.

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

Completeness3/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 good annotations, the description covers purpose and return basics. However, it does not explain the 'number_show' parameter or mention pagination/record limits, leaving a gap for agents trying to use the tool correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It clarifies 'years' as 'specified number of years ago', but completely omits explanation of 'number_show', leaving its meaning and constraints (max 100) undocumented in both schema and description.

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 lists births a specified number of years ago, using a specific verb and resource. It distinguishes itself from the sibling get_births by focusing on the 'years ago' filter, and the version note adds further specificity.

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 description implies usage for querying births exactly N years ago but does not explicitly compare with alternatives like get_births or state when not to use this tool. No explicit exclusions or alternative references are provided.

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

All Open Archives toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources