Skip to main content
Glama
Sign In
oyama-opendata-mcp

oyama-opendata-mcp

by bishi-eava
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

年齢構成（人口ピラミッド）

get_age_distribution

Retrieve population by 5-year age groups and gender. Filter by district or month for targeted data. Ideal for population pyramid visualizations.

Instructions

5歳階級×男女別の人口構成を返す。yearMonth未指定なら最新月、district指定で地区別、未指定で市全体に合算。人口ピラミッドの描画に使える。

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

Input Schema

NameRequiredDescriptionDefault
districtNo地区名で絞り込み（未指定なら市全体）
yearMonthNo対象年月（未指定なら最新月）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It explains aggregation logic and defaults, but does not mention read-only nature, rate limits, or response format.

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?

Two concise sentences with front-loaded main purpose. Every sentence adds value with no wasted words.

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

Completeness5/5

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

With 2 optional parameters, no output schema, and no annotations, the description fully covers the tool's behavior and usage context.

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

Parameters4/5

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

Schema coverage is 100%, but description adds meaningful context about defaults and aggregation behavior beyond the schema descriptions.

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?

Description clearly states it returns population composition by 5-year age groups and gender, distinguishing it from sibling tools like get_population and list_areas.

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

Usage Guidelines4/5

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

Explicitly describes default behavior for optional parameters (latest month if yearMonth unspecified, district aggregation vs. city-wide) and mentions use case for population pyramid drawing. Does not mention when not to use or compare to 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