Belgium Art — places, tours and transfers

Выбрать следующие вопросы

get_questions

Read-onlyIdempotent

Get available questions by context. Titles come from published native blocks or reviewed navigation metadata indexing complete current author passages; navigation titles are not verbatim article headings. Use after_question_id for linked follow-ups; exclude_ids removes questions already discussed. Follow-ups may belong to a different entity; use the returned entity_id. Optional next_steps are separate; do not repeat a tour invitation in every answer.

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": {
      "place_id": "<place_id>"
    },
    "name": "get_questions"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`context`	No
`place_id`	Yes
`exclude_ids`	No
`after_question_id`	No

Output Schema

Name	Required	Description	Default
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds real context beyond them: titles are not verbatim headings, follow-ups may cross entities so the returned entity_id should be used, and next_steps are separate with a caution against repeating tour invitations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening purpose is front-loaded, but the title-provenance sentence is jargon-dense ('reviewed navigation metadata indexing complete current author passages') and partly redundant with the clarifying clause that follows it. Some compression would improve readability without losing information.

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?

An output schema exists, so return values need not be explained. The description still usefully mentions the returned entity_id and optional next_steps, which helps an agent chain calls. Remaining gaps are the unexplained context enum values and limit semantics.

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

Parameters3/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. It explains after_question_id and exclude_ids meaningfully, but place_id, limit (1-12 bound), and the five context enum values (all/before/onsite/children/deeper) receive no explanation, leaving half the parameters 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 and resource ('Get available questions by context') and clarifies where titles come from. It does not explicitly differentiate itself from siblings like get_answer or search_knowledge, so an agent must infer the boundary.

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 guidance is implied through parameter hints ('Use after_question_id for linked follow-ups; exclude_ids removes questions already discussed'), but there is no explicit statement of when to pick this tool over get_answer or search_knowledge, nor any exclusions.

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

All Belgium Art — places, tours and transfers tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?