Skip to main content
Glama

Roll a random birth in human history (1 CE–2025)

roll_random_birth
Read-onlyIdempotent

Draw a random human birth weighted by how many people were actually born in each place and century/decade between 1 CE and 2025 (or within a chosen year), returning the birthplace, odds, life expectancy, historical events during that lifetime, and a playable BornThen link for those five lives.

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

Input Schema

NameRequiredDescriptionDefault
seedNoOptional deterministic alphanumeric seed so the same call reproduces the same birth.
yearNoOptional birth year (1–2025). Omit to draw across all human births since 1 CE.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the population-weighted sampling method and the specific outputs (birthplace, odds, life expectancy, historical events, playable link). It does not clarify how randomness interacts with idempotentHint=true, though the seed parameter in the schema explains determinism.

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

Conciseness4/5

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

It is a single front-loaded sentence that puts the core action first and the output inventory second, with no filler. It is somewhat run-on, packing weighting, scoping, and five return values into one clause chain, but nothing is wasted.

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?

With only two optional, fully documented parameters and no output schema, the description does a good job enumerating what comes back. The main completeness gap is that it never explains the seed-based reproducibility contract or how the weighting is computed, though both are minor for a read-only sampling tool.

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 description coverage is 100%, so both parameters (seed and year) are already fully documented with patterns and ranges, establishing the baseline of 3. The description only reiterates the optional year scoping and adds nothing about seed behavior that the schema doesn't already state.

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 uses a specific verb and resource ('Draw a random human birth') and adds the weighting model (births per place and century/decade) plus the full return payload, so the tool is unmistakable. It never names or contrasts the sibling query_era_facts, which keeps it just short of the top mark.

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?

Usage is implied rather than stated: the parenthetical '(or within a chosen year)' hints that a year scopes the draw, but the explicit rule to omit year for an all-history draw lives in the schema, not the description. There is no when-not-to-use guidance and no reference to alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.