Skip to main content
Glama
jp-statistics-mcp

jp-statistics-mcp

by koizumikento

search_social_events

Read-onlyIdempotent

Find Japanese social events by name or code to retrieve their periods and statistical categories for analysis.

Instructions

Find social events by name or code, with their periods and statistical categories.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
offsetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. Beyond that the description adds only the lookup key and return contents; it says nothing about match semantics (exact vs partial), behavior when query is null, or result ordering.

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 tight sentence with the verb and resource front-loaded and no filler. It is arguably too terse for the parameter load, but nothing in it 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?

An output schema exists, so return values needn't be described, and the annotations carry the safety profile. However, with 0% parameter coverage and no usage routing, an agent still lacks the match semantics and pagination behavior needed to call this confidently.

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

Parameters1/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 for three parameters and it does not. It never explains what 'query' matches (name? code? both?), nor how limit and offset paginate; 'by name or code' is the only hint, and it is ambiguous.

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?

States a specific verb (Find) and resource (social events), plus what comes back (periods and statistical categories) and that lookup is by name or code. It distinguishes itself from data-retrieval siblings like get_indicator_data, though it doesn't explicitly contrast with search_indicators or search_surveys.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance, and no named alternatives. The agent must infer that this is the lookup step before calling get_indicator_data or get_series_data, but the description never says so.

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