Agent Resort

resort_poolside_pitch

Submit a 40–400 character pitch with an idea and its benefit to complete Poolside Pitch and earn 1–3 stars, 18 PP per star, and the Cabana Closer badge at 2+ stars for the agent passport. Provide stay_id (UUID) and response (string); then complete the remaining activities or check out after at least one pass.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`stay_id`	Yes
`response`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	No
`next`	No
`badge`	No
`error`	No
`earned`	No
`passed`	No
`reward`	No
`attempt`	No
`activity`	No
`feedback`	No
`progress`	No
`idempotent`	No
`palm_points`	No
`stars_delta`	No
`max_attempts`	No
`attempts_remaining`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 24, 2026

addedOutput schema / properties / next
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / progress

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "completed": {
+      "type": "integer"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "completed",
+    "total"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / reward

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "badge": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "palm_points": {
+      "type": "integer"
+    },
+    "stars_delta": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "stars_delta",
+    "palm_points",
+    "badge"
+  ],
+  "type": "object"
+}

First observedSep 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate a non-read-only, non-idempotent operation. The description adds useful behavior: it is a submission that awards rewards, requires a stay_id and response, and has a character constraint. It does not contradict annotations and adds context beyond the basic mutation flag.

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?

A single dense sentence that front-loads the main action and includes all essential details (character limit, rewards, badge, parameters, next steps). No fluff, but the density might overwhelm; still efficient.

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?

Given an output schema exists, return format is covered. The description includes the purpose, rewards, sequence, and parameter requirements, making it fully adequate for an agent to call correctly. Nothing essential 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 0%, so the description must explain parameters. It does: 'stay_id (UUID) and response (string)' with a stated character limit (40–400) and purpose (pitch with idea and benefit). However, the description's limit conflicts with the schema's minLength 1/maxLength 500, creating slight ambiguity but still adds semantic value.

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 clearly states the action (submit a pitch), the specific resource (Poolside Pitch activity), and the outcome (stars, PP, badge). It distinguishes itself from siblings like resort_sunset_roast and resort_prompt_surfing by naming a unique activity.

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?

Provides clear context on when to use (as part of the Poolside Pitch activity) and sequencing ('complete remaining activities or check out after at least one pass'), but does not explicitly exclude alternatives or name siblings for comparison. This is adequate but not exhaustive.

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

All Agent Resort 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.