Skip to main content
Glama

Validate a note on a Nexez booking

nexez_validate_booking_note
Read-only

Dry-run adding a note to an appointment the buyer already booked. Needs the buyer's own booking link (the orderUrl returned when it was booked). Returns the note for the buyer to approve before using the returned handoff. Notes lock when the appointment starts. Never sends the 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": {
      "order": "<order>",
      "note": "<note>"
    },
    "name": "nexez_validate_booking_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesPlain-text note, up to 1,000 characters. No Social Security, card, bank or wiring details.
orderYesThe buyer's booking link (orderUrl), exactly as returned when the appointment was booked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with them ('Dry-run', 'Never sends the note'), reinforcing rather than repeating. It adds genuinely new behavior: the returned note goes to the buyer for approval, and a 'returned handoff' is the artifact to use afterward. The undefined notion of a 'handoff' is the one gap in an otherwise informative behavioral account.

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?

Five short sentences, front-loaded with the dry-run framing and the required input, and every sentence contributes a constraint or behavior. The phrase 'before using the returned handoff' is slightly opaque and a cleaner statement of the next step would tighten it.

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 two-parameter, non-destructive validation tool with no output schema, the description covers purpose, prerequisites, the no-side-effect guarantee, and the temporal lock. What an agent still lacks is any characterization of the returned validation result (e.g., what a rejection looks like), which matters for a tool whose whole job is validation.

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 100%, so both parameters are already documented with their formats and content restrictions. The description restates the orderUrl provenance but adds no format, escaping, or edge-case detail beyond the schema. Baseline 3 is appropriate when the schema carries the semantics.

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 uses a specific verb+resource ('Dry-run adding a note to an appointment') and states the scope ('never sends the note'), so the agent can tell this is a validation-only operation. It does not name a sibling contrast explicitly, but the dry-run framing plus 'never sends' implicitly separates it from a real note-submission path.

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?

It states the precondition clearly ('an appointment the buyer already booked') and the required input provenance ('the orderUrl returned when it was booked'). It also gives the temporal constraint 'Notes lock when the appointment starts', which tells the agent when this call is still viable. It stops short of naming an alternative tool for the actual submission, so it is clear context rather than full when/when-not routing.

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