erphome.pl

Get Reservation

get_reservation

Read-onlyIdempotent

Get a single reservation by id.

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": {
      "id": "<id>"
    },
    "name": "get_reservation"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Reservation id, from list_reservations.

Output Schema

Name	Required	Description	Default
`data`	Yes
`help_url`	No	Help-center article with step-by-step instructions for this area. Show it to the user when they need to change something in the panel.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

addedOutput schema / properties / help_url

Added value: +{
+  "description": "Help-center article with step-by-step instructions for this area. Show it to the user when they need to change something in the panel.",
+  "type": "string"
+}

First observedSep 10, 2026

TDQS

B3.1/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=false, so the safety profile is fully covered elsewhere. The description adds no behavioral context of its own (no error behavior for missing ids, no permission notes), so it contributes nothing beyond the structured data.

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 short sentence with zero filler and the key scope ('single', 'by id') front-loaded. It is efficient, though its brevity borders on under-specification rather than maximal usefulness.

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, the input schema is fully described, and annotations cover the safety profile, so the agent has what it needs to invoke the tool correctly. The description itself is minimal but the surrounding structured data fills the gaps.

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?

Only one parameter exists and the schema already documents it at 100% coverage, including the helpful note that the id comes from list_reservations. The description adds no format or semantics beyond the schema, so the baseline of 3 applies.

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 verb (Get) and resource (a single reservation) scoped to one item by id, which is clear and unambiguous. It does not, however, distinguish itself from the sibling list_reservations or explain the singular-vs-list boundary, so it falls short of the 5 tier.

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?

There is no explicit when-to-use guidance, no mention of list_reservations as the alternative when the id is unknown, and no prerequisites stated. Usage is only weakly implied by the phrase 'by id'.

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

All erphome.pl 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?