Skip to main content
Glama

施設の検証済み詳細

get_hotel
Read-onlyIdempotent

slug指定で施設の全条件(施設別の根拠note付き)・キッズ設備・アクセス・出典・検証日を返します。

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": {
      "slug": "<slug>"
    },
    "name": "get_hotel"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes施設slug(search_hotelsの結果に含まれる)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare a read-only, idempotent, non-destructive, closed-world lookup, so the safety profile is covered. The description adds genuine value by disclosing that results carry per-facility evidence notes, sources and a verification date, but it says nothing about what happens if the slug is unknown or about any auth/limit constraints.

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?

One compact sentence that front-loads the keyed lookup and enumerates the returned content without filler. It is dense but every clause describes an actual output component.

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 one-parameter read tool with full annotation coverage and no output schema, the description adequately enumerates what comes back (conditions with evidence, kids facilities, access, sources, verification date). Missing only failure/empty-result behavior.

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% and the single slug parameter is already documented with its provenance (search_hotels results). The description reinforces that the entire result is keyed off the slug, so the baseline is met and slightly exceeded.

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 and resource: returns a facility's full conditions, kids facilities, access, sources and verification date by slug. That is clearly distinguishable from list_areas/list_conditions and the search_hotels sibling, 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?

Usage is only implied: the slug requirement and the schema's note that slugs come from search_hotels results show this is the follow-up detail call. There is no explicit when-to-use/when-not statement or named alternative.

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