chucho — Book Direct

Record anonymous property interaction

record_property_event

For the property-card UI only: record a property view or successful outbound host-link action. Accepts only a public property ID, a temporary random session UUID, event type and language. Never send conversation text, contacts or URLs. This does not book a stay.

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>",
      "type": "<type>",
      "sessionId": "<sessionId>",
      "locale": "<locale>"
    },
    "name": "record_property_event"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`type`	Yes
`locale`	Yes
`sessionId`	Yes

Output Schema

Name	Required	Description	Default
`accepted`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026
- removedOutput schema / additionalProperties
```
Removed value: -false
```
First observedOct 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds real context beyond the annotations: a strict data-minimization contract ('Accepts only... Never send conversation text, contacts or URLs') and an explicit negative behavior (does not book). Annotations already mark it non-read-only, non-idempotent and closed-world, so the remaining gap is minor — it doesn't say where the event lands or whether duplicate calls inflate counts.

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?

Three short sentences, zero filler, and the scoping constraint is front-loaded before the privacy rules and the negative behavior. Every sentence contributes a distinct constraint.

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 non-read-only, non-idempotent event logger the description covers scope, allowed payload, prohibited payload and the booking confusion case; the output schema means return values need not be described. Only the downstream effect of the event (analytics sink, duplicate handling) is left implicit.

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?

With 0% schema description coverage the description must carry the load, and it does: 'public property ID', 'temporary random session UUID', 'event type', and 'language' map onto all four required parameters, and 'property view or successful outbound host-link action' resolves the two enum values. It doesn't spell out the accepted locale values or the UUID format, which the schema supplies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (record a property view or outbound host-link action) and pins the scope to the property-card UI, which immediately separates it from the rest of the catalog. The final clause ('This does not book a stay') actively rules out confusion with the booking/enquiry siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the exact UI surface where it applies ('property-card UI only') and gives a clear exclusion ('does not book a stay'), which is strong when-to-use guidance. It stops short of naming the sibling an agent should call instead when a booking, enquiry, or quote is actually wanted.

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

All chucho — Book Direct 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?