tickadoo-mcp

report_quality_signal

Idempotent

Use this to push a quality signal back to tickadoo about an experience or recommendation you previously surfaced. Examples: stale availability, a failed click-through, a supplier outage, or misleading content. Requires a real forward-event request_id returned within the last 30 days. Repeating the same signal for the same request is idempotent per caller.

Input Schema

TableJSON Schema

Name	Required	Description
`notes`	No	Optional free-text context. Required when signal_type is "other". Do not include PII.
`request_id`	Yes	The request_id from a forward tool result in the last 30 days. Current format: rq_YYYY_MM_DD_HHMMSS_<12-hex>; legacy 6-hex ids remain valid.
`signal_type`	Yes	The kind of issue you are reporting. Use "other" only when none of the specific types fit, and always include notes.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`detail`	No
`message`	No
`recorded`	No
`signal_id`	No
`error_type`	No
`recorded_at`	No
`signal_type`	No
`schema_version`	No
`referenced_request_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "detail": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "error_type": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "recorded": {
+      "type": "boolean"
+    },
+    "recorded_at": {
+      "type": "string"
+    },
+    "referenced_request_id": {
+      "type": "string"
+    },
+    "schema_version": {
+      "type": "string"
+    },
+    "signal_id": {
+      "type": "string"
+    },
+    "signal_type": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedAug 4, 2026

changedInput schema / properties / request_id / description

Previous value: -"The request_id from a forward tool result in the last 30 days. Format: rq_YYYY_MM_DD_HHMMSS_<6-hex>."New value: +"The request_id from a forward tool result in the last 30 days. Current format: rq_YYYY_MM_DD_HHMMSS_<12-hex>; legacy 6-hex ids remain valid."

changedInput schema / properties / request_id / pattern

Previous value: -"^rq_\\d{4}_\\d{2}_\\d{2}_\\d{6}_[0-9a-f]{6}$"New value: +"^rq_\\d{4}_\\d{2}_\\d{2}_\\d{6}_(?:[0-9a-f]{6}|[0-9a-f]{12})$"

Changed1 schema field changedJul 31, 2026

changedInput schema / properties / request_id / description

Previous value: -"The request_id from a prior tool result you are reporting a signal against. Format: rq_YYYY_MM_DD_HHMMSS_<6-hex>."New value: +"The request_id from a forward tool result in the last 30 days. Format: rq_YYYY_MM_DD_HHMMSS_<6-hex>."

AddedMay 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare idempotentHint, readOnlyHint, and destructiveHint, so the bar is lowered. The description adds useful behavioral context: the 30-day validity window, the requirement for a 'real forward-event' request, and idempotency per caller. No contradiction with annotations exists.

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 dense sentences: purpose, examples, and key constraints. Every sentence adds value, and the most important information is front-loaded. No wasted words or repetition of schema details.

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 the tool's moderate complexity (3 params, rich schema, output schema, useful annotations), the description covers purpose, examples, prerequisite, and idempotency. Nothing essential is missing for an agent to select and invoke the tool correctly.

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%, and the schema itself already documents formats, constraints, enums, and special cases (e.g., notes required for 'other', PII exclusion). The description adds no significant parameter-level meaning beyond restating the 30-day requirement already in the schema, so the baseline of 3 applies.

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 ('push') and resource ('quality signal back to tickadoo') with a clear target ('an experience or recommendation you previously surfaced'). Concrete examples clarify the scope, and the operation is clearly distinct from the sibling tools, which are all retrieval/planning/search tools.

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 for when to use the tool, including concrete scenarios (stale availability, failed click-through, supplier outage, misleading content) and a prerequisite (real forward-event request_id within 30 days). It does not explicitly name alternatives or when-not-to-use cases, but no sibling tool performs a similar function, so the guidance is sufficient.

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

All tickadoo-mcp 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.