Déstaire

Buy a city guide

buy_guide

Idempotent

Buy a city guide for the user, paid inside this conversation. Gives a pay link that takes an MPP payment (a Stripe Shared Payment Token from your wallet, such as Link). Confirm the user's email first: the guide goes to that account, and the purchase is final.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	The guide's slug, the last part of its URL.
`email`	Yes	The user's email address: the guide goes to this Déstaire account.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`email`	Yes
`guide`	Yes
`price`	Yes
`paymentLink`	Yes
`instructions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 28, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- changedOutput schema / properties / guide / additionalProperties
```
Previous value: -falseNew value: +{}
```
- changedOutput schema / properties / instructions / additionalProperties
```
Previous value: -falseNew value: +{}
```

Changed4 schema fields changedSep 25, 2026

addedOutput schema / properties / guide / properties / city
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / guide / properties / country
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / guide / properties / cover

Added value: +{
+  "anyOf": [
+    {
+      "format": "uri",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / guide / required

Previous value: -[
-  "title",
-  "url"
-]New value: +[
+  "title",
+  "url",
+  "city",
+  "country",
+  "cover"
+]

AddedSep 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the payment mechanism (MPP payment, Stripe Shared Payment Token from the user's wallet such as Link), that a pay link is returned, that delivery is tied to the email account, and that the purchase is final and non-refundable. That irreversibility and payment-flow context is exactly what annotations like destructiveHint=false cannot convey.

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 tight sentences, front-loaded with what the tool does and the payment model, followed by the prerequisite and the finality warning. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be enumerated, yet the description still previews the pay link. Combined with payment method, delivery target, prerequisite, and non-refundability, everything an agent needs to call this safely is present.

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, and the description largely restates the email parameter's purpose ('the guide goes to that account') while adding the actionable requirement to confirm it with the user. The slug parameter gets no additional semantic detail. Baseline 3 is appropriate.

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 ('Buy a city guide for the user') and immediately qualifies the transaction model ('paid inside this conversation'), which separates it from the read-only get_guide/list_guides siblings. An agent knows exactly what this tool does 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 Guidelines4/5

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

Gives a clear prerequisite ('Confirm the user's email first') and frames this as a paid purchase, which implicitly contrasts with the free read siblings. It never explicitly names get_guide as the alternative for reading, so the when-not-to-use routing is left to inference.

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

All Déstaire 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?