Skip to main content
Glama

データカタログと鮮度・欠損

get_tubesaku_data_catalog
Read-onlyIdempotent

公開データの一覧、更新日時、観測範囲、欠損・古さ・利用条件を確認する。観測日時と欠損情報を含む。

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_tubesaku_data_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful content-level behavior by stating that observation datetime and missing-data information are included, but it does not describe response shape, pagination, or any access constraints, so it adds only moderate value beyond the annotations.

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?

The description is two short, front-loaded sentences that state the catalog contents and then the included metadata. The second sentence partly repeats 欠損 from the first, but overall it is efficient and easy to scan.

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?

For a zero-parameter, read-only catalog tool with full annotation coverage and no output schema, the description covers the essential purpose and the key metadata returned. It could say more about the response format or ordering, but nothing critical for invoking the tool is missing.

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?

There are zero input parameters, so the baseline is 4 and no parameter-level explanation is required. The description does not need to compensate for any schema coverage gap.

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 states a specific resource (公開データの一覧 / public data catalog) and enumerates the metadata it exposes: update timestamps, observation range, missingness, staleness, and usage conditions. The verb 確認する ('check/confirm') is slightly generic, and it does not explicitly distinguish itself from nearby tools such as get_tubesaku_index or get_tubesaku_service_info, which keeps it from a 5.

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?

It implies the tool is for inspecting catalog freshness and coverage, but gives no explicit when-to-use guidance, no when-not-to-use conditions, and no named alternatives among the sibling tools. An agent must infer whether to call this versus get_tubesaku_index or get_tubesaku_service_info.

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.

Resources