Skip to main content
Glama

Query historical era demographics and events

query_era_facts
Read-onlyIdempotent

Look up BornThen demographic figures (population, life expectancy, child mortality, literacy, urbanisation, each labelled statistic / estimate / model) and sourced historical events (wars, famines, plagues, depressions) by year, period slug (e.g. "1920s", "14th-century"), place, or event keyword.

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

Input Schema

NameRequiredDescriptionDefault
yearNoYear between 1 CE and 2025.
placeNoISO3 country code (e.g. "GBR", "CHN", "IND") or historical region id (e.g. "mesopotamia", "north-china", "western-europe").
event_queryNoKeyword or event id to search historical events (e.g. "black death", "great depression", "famine").
period_slugNoDecade or century slug such as "1920s", "1840s", "14th-century", or "1st-century".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add genuinely useful context that statistics are labelled statistic/estimate/model and that events are sourced, but it omits result limits, pagination, and the behaviour of an unfiltered (no-parameter) call.

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?

A single front-loaded sentence: the resource is named first, then the query dimensions, then the value formats. It is dense but every clause carries information; the only mild cost is the parenthetical enumeration load.

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?

With no output schema, the description compensates well by naming the returned data domains and the statistic/estimate/model labelling. For a 4-parameter, all-optional tool the remaining gap is what an empty call returns, which leaves one real ambiguity unresolved.

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 the schema already documents every parameter, including formats and examples. The description adds only that period slugs are decade/century style and that events are keyword-searchable, which is largely redundant with the schema examples — baseline 3 applies.

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 gives a precise verb+resource pair: 'Look up BornThen demographic figures ... and sourced historical events', and enumerates the exact data domains (population, life expectancy, child mortality, literacy, urbanisation) plus the event categories. This is unmistakably distinct from the only sibling, roll_random_birth, without needing to read any schema.

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?

It states the four lookup axes (year, period slug, place, event keyword) and gives example values, which implies how to query. However, it never says when this tool is preferred over alternatives, whether axes can be combined, or what happens when no parameter is supplied — notable given required parameters is zero.

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.