Skip to main content
Glama

53条件の定義一覧

list_conditions
Read-onlyIdempotent

検索に使える子連れ条件の全定義(id・ラベル・対象年齢・該当施設数)を返します。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond them by enumerating the returned fields (id, label, target age, applicable facility count), which matters because there is no output schema, and 全て makes clear the result is the complete set with no pagination.

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?

One sentence, front-loaded with the verb and resource, and every clause (fields returned, 全て, 検索に使える) carries information. No redundant restatement of the title.

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, zero-output-schema enumeration tool, the description supplies the missing return-shape information, which is the main gap an agent faces here. The only shortfall is the absence of explicit guidance tying the returned ids to the search flow.

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?

The tool takes zero parameters, so the baseline is 4; nothing needs explanation and the description correctly implies an unfiltered full dump. It does not invent parameter-like filtering that would mislead.

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?

Names a specific verb (返します) and a precisely scoped resource (子連れ条件の全定義) plus the four fields each entry carries (id・ラベル・対象年齢・該当施設数). The resource is clearly distinct from the sibling tools list_areas / get_hotel / search_hotels, though no sibling is named explicitly.

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?

The phrase 検索に使える implies this is a reference lookup used to discover valid search condition ids, but the description never states when to call it versus search_hotels, nor that its ids feed the search filter. Usage is implied rather than stated.

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