Skip to main content
Glama

See Nexez booking options

nexez_booking_options
Read-only

For a listing that books appointments on Nexez. With only a slug: the services that book there, each with its length, price, ways to meet, rules, and whether an assistant can book it. With a slug and a service: the open times from the seller's rules (ISO instants, with the seller's time zone), the details every booking needs, and the seller's own questions, each marked assistantMayAnswer true (fill it in from what the buyer already said) or false (ask the buyer directly). Read-only.

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": "nexez_booking_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesExact published listing slug returned by discovery, not a full URL.
serviceNoService id from a previous nexez_booking_options call, for example buyer-consultation. Omit to list the services.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint, yet the description still adds real behavioral context: times are ISO instants expressed in the seller's time zone, rules drive availability, and each seller question carries assistantMayAnswer with the instruction to fill true values from prior buyer context and ask the buyer for false ones. The trailing 'Read-only.' merely restates the annotation and adds nothing.

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?

It is tightly front-loaded around the two calling modes and every clause carries information about the returned payload. The telegraphic colon-based phrasing is dense but readable; the closing 'Read-only.' is redundant with readOnlyHint=true.

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?

With no output schema, the description carries the burden of explaining return values, and it does so for both modes down to field-level semantics like assistantMayAnswer. Minor gaps remain around failure behavior for an unknown slug or service and whether results are paginated, but nothing essential to a correct call is missing.

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%, so the baseline is 3, but the description adds meaning the schema does not: omitting 'service' changes the entire response shape, and the service id must come from a prior call's output. That conditional semantics is genuinely useful beyond the field descriptions.

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?

The description opens with the precondition ('a listing that books appointments on Nexez') and then states the two distinct result shapes: services with length, price, meeting modes and rules, versus open times, required booking details and seller questions. An agent can tell exactly what resource is being read and how the output changes with its arguments.

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 gives explicit branching guidance tied to parameters ('With only a slug' vs 'With a slug and a service'), which effectively covers when to use each mode. It does not, however, say when to use this tool instead of a sibling validation tool or what to do if the slug is wrong, so it stops short of full when/when-not coverage.

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