Skip to main content
Glama

Surfing Dog Inbox

by ai.surfingdog
OverviewDiscussionsAdmin

Request a booking

create_booking
Idempotent

Request a service at a time. Check availability first. A fixed-price service costs the business's price from list_services; a different totalPrice you send is only noted for the business. A priced booking binds your person only once they confirmed it: without terms_sha nothing is sent, and you get the summary to show them (confirm.summary, confirm.terms_sha); call again with that terms_sha on their clear yes. Returns the item and, if you have no account, an access_token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoThe person's key (sdkey1_…), if that is all you have: it is exchanged once for a pass, which comes back in identity.passes — keep the pass and send it next time instead. Never stored.
passNoThe person's passes (sdpass1_…), space-separated, at most 8: presented to the network that issued each, so the business recognises the customer. Or send them in the Sdi-Pass header. Never stored.
contactNo
messageNo
payloadYes
terms_shaNoThe fingerprint of the terms your person confirmed (details.terms_sha of the 409 confirm_terms a priced request without it gets). Nothing is sent to the business without it when the request carries a price.
idempotency_keyNoSame key + same request = same answer. Required for agents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / payload / properties / personalised
      Added value: +{
+  "properties": {
+    "listPrice": {
+      "properties": {
+        "currency": {
+          "maxLength": 3,
+          "minLength": 3,
+          "type": "string"
+        },
+        "value": {
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "value",
+        "currency"
+      ],
+      "type": "object"
+    },
+    "says": {
+      "maxLength": 200,
+      "type": "string"
+    }
+  },
+  "required": [
+    "listPrice"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / terms_sha
      Added value: +{
+  "description": "The fingerprint of the terms your person confirmed (details.terms_sha of the 409 confirm_terms a priced request without it gets). Nothing is sent to the business without it when the request carries a price.",
+  "pattern": "^[A-Za-z0-9_-]{43}$",
+  "type": "string"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover read-only/idempotent/destructive hints, so the description carries the real behavioral load and does: it discloses the two-step priced-booking confirmation flow, that nothing is transmitted without terms_sha, that a differing totalPrice is only noted for the business, and that a no-account caller receives an access_token. These are meaningful traits beyond the structured hints.

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?

Front-loaded with the core action and prerequisite, then pricing, then the confirmation flow, then the return. Every sentence carries distinct information with no filler.

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 complex, 7-param, nested-object, no-output-schema tool, the description covers purpose, prerequisite, pricing nuance, confirmation gating, and return shape. Minor gaps remain around how a fixed-price vs priced booking is determined and the idempotency_key requirement, but the essentials are present.

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 57% schema coverage, the schema documents key/pass/terms_sha but the description adds genuine meaning about totalPrice semantics (fixed-price from list_services vs. a noted-only different totalPrice) and reiterates the terms_sha gate. It does not clarify the nested payload fields, though those are largely defined in the schema.

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 and resource ("Request a service at a time") and immediately differentiates itself from related siblings by pointing to check_availability and list_services. An agent can tell this is the booking-creation tool without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit sequencing ("Check availability first") and a clear when/when-not: a priced booking without terms_sha sends nothing, and the agent must call again with the terms_sha on the customer's clear yes. Both the prerequisite and the confirmation gate are spelled out, leaving little to inference.

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

All Surfing Dog Inbox toolsInspect
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