events_offersLive and scheduled public offers at an event: title, which booth, the time window in minutes and remaining-count style numbers.
| Name | Required | Description | Default |
|---|---|---|---|
| eventIdOrSlug | Yes | Event id, public slug, or the event name as events_list spells it; short forms such as "the stroll" work. |
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| found | No | ||
| offers | No | ||
| drawing | No | ||
| eventId | No | ||
| message | No | ||
| raffles | No | ||
| endedCount | No | ||
| offerCount | No |
Changes observed during successful MCP inspections.
Input schema / properties / eventIdOrSlug / descriptionPrevious value: -"Event id (belmont_stroll), public slug (cba26), or the event NAME as events_list spells it (\"Summer Stroll & Savor\"). Common short forms work too (\"the stroll\", \"tie summit\")."New value: +"Event id, public slug, or the event name as events_list spells it; short forms such as \"the stroll\" work."Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "anyOf": [
+ {
+ "required": [
+ "found",
+ "eventId",
+ "offerCount",
+ "endedCount",
+ "offers",
+ "raffles"
+ ]
+ },
+ {
+ "properties": {
+ "ok": {
+ "const": false
+ }
+ },
+ "required": [
+ "ok"
+ ]
+ },
+ {
+ "properties": {
+ "found": {
+ "const": false
+ }
+ },
+ "required": [
+ "found"
+ ]
+ },
+ {
+ "required": [
+ "error"
+ ]
+ }
+ ],
+ "properties": {
+ "drawing": {
+ "type": "object"
+ },
+ "endedCount": {
+ "type": "integer"
+ },
+ "error": {
+ "type": "string"
+ },
+ "eventId": {
+ "type": "string"
+ },
+ "found": {
+ "type": "boolean"
+ },
+ "message": {
+ "type": "string"
+ },
+ "offerCount": {
+ "type": "integer"
+ },
+ "offers": {
+ "items": {
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "raffles": {
+ "items": {
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds that results are limited to public offers and include live/scheduled states plus remaining-count numbers, but it does not mention pagination, ordering, or whether private offers exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A compact, front-loaded sentence fragment with no wasted words. It could be strengthened with an explicit verb, but every clause carries useful information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only single-parameter list tool with a rich output schema and clear annotations, the description is largely sufficient. It does not cover pagination or ordering, but those are minor given the output schema exists.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single eventIdOrSlug parameter is fully documented in the schema, including slug/name flexibility. The description adds no meaning beyond that, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States the resource (public offers at an event) and scope (live and scheduled), with the fields returned. It is clear what the tool fetches, though it does not explicitly contrast itself with siblings like events_whats_on or events_booths.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by the phrase 'live and scheduled public offers at an event', but there is no explicit when-to-use, when-not-to-use, or alternative named. An agent must infer that this is the offers-specific listing rather than the general events_whats_on.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.