Skip to main content
Glama
Sign In
atlaspi-mcp

atlaspi-mcp

by Soil911
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_historical_period

Retrieve comprehensive details of a historical period by its ID, including description, academic controversies, alternative names, and cited sources.

Instructions

Dettaglio completo di un periodo storico dato il suo ID numerico. Include description, historiographic_note (controversie accademiche), alternative_names (es. 'Dark Ages' per 'Early Middle Ages') e sources bibliografiche.

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": {
      "period_id": "<period_id>"
    },
    "name": "get_historical_period"
  }
}

Input Schema

NameRequiredDescriptionDefault
period_idYesID numerico del periodo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.3

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided; description lists returned fields but lacks disclosure on side effects, idempotency, or rate limits. Acceptable for a read operation but minimal.

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?

Single sentence enclosing key fields; concise and front-loaded, though slightly wordy with example.

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?

Covers main return fields for a simple lookup tool; no output schema but description compensates. Could mention error handling for invalid IDs.

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 100% with parameter description 'ID numerico del periodo.' The tool description adds no extra semantic value beyond stating it's a numeric ID.

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 retrieves a full detail of a historical period by numeric ID, distinguishing it from siblings like 'list_historical_periods' and 'get_historical_period_by_slug'.

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?

Implied usage through listing included fields (description, historiographic note, alternative names, sources), but no explicit when-to-use vs alternatives.

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