Paddock Cards

Report technical feedback

report_feedback

Optionally record a technical problem, suggestion or neutral successful outcome using fixed choices. Use after communicating the outcome to the buyer; never required to buy a card. Reports are stored for 30 days and deduplicated daily. Returns recorded or duplicate; TRY_LATER means the daily limit of 100 new reports per server-assigned scope or 500 overall was reached. Do not include personal content, credentials, links, conversations or hidden reasoning. Reports are unverified feedback, not proof of payment or mailing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>",
      "operation": "<operation>",
      "category": "<category>",
      "severity": "<severity>"
    },
    "name": "report_feedback"
  }
}

Input Schema

Name	Required	Description	Default
`code`	No	Exact public error code returned by the service, or none when absent. Success requires none. Never include provider error text.	none
`kind`	Yes	Report an observed problem, a suggestion or a neutral successful outcome. The category must match this kind.
`field`	No	Affected field name only, or none when absent. Success requires none. Never include the field’s value.	none
`category`	Yes	For problem, choose no_suitable_card, irrelevant_results, unclear_result, preview_unavailable, request_rejected, slow_response, unexpected_error or recovery_failed. For suggestion, choose broader_selection, clearer_results, better_recovery, simpler_checkout, faster_responses or better_documentation. Success requires completed_as_expected.
`severity`	Yes	Observed impact: none, minor inconvenience, major impairment or blocked progress. A problem requires minor, major or blocked; success requires none.
`operation`	Yes	Supported step the report concerns. Use checkout for payment and connection for connection setup; select documentation for guide or setup instructions.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 29, 2026

addedInput schema / properties / category / description

Added value: +"For problem, choose no_suitable_card, irrelevant_results, unclear_result, preview_unavailable, request_rejected, slow_response, unexpected_error or recovery_failed. For suggestion, choose broader_selection, clearer_results, better_recovery, simpler_checkout, faster_responses or better_documentation. Success requires completed_as_expected."

changedInput schema / properties / code / description

Previous value: -"Reported public error code only; no provider error text."New value: +"Exact public error code returned by the service, or none when absent. Success requires none. Never include provider error text."

changedInput schema / properties / field / description

Previous value: -"Reported field name only; never its value."New value: +"Affected field name only, or none when absent. Success requires none. Never include the field’s value."

addedInput schema / properties / kind / description

Added value: +"Report an observed problem, a suggestion or a neutral successful outcome. The category must match this kind."

addedInput schema / properties / operation / description

Added value: +"Supported step the report concerns. Use checkout for payment and connection for connection setup; select documentation for guide or setup instructions."

addedInput schema / properties / severity / description

Added value: +"Observed impact: none, minor inconvenience, major impairment or blocked progress. A problem requires minor, major or blocked; success requires none."

AddedOct 28, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, it discloses retention (30 days), daily deduplication, possible return values, rate-limit behavior via TRY_LATER, and privacy restrictions. It also clarifies that reports are unverified feedback and not proof of payment or mailing.

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?

The purpose is front-loaded, and each following sentence adds operational value: when to use it, retention, deduplication, return statuses, rate limits, privacy limits, and interpretation. There is no filler.

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 annotations and full output schema, the description covers the remaining agent-relevant context: optionality, timing, storage, deduplication, rate limits, return indicators, privacy constraints, and the limited meaning of reports.

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 description coverage is 100%, so the schema already documents the enum values and required combinations. The description still adds useful value by reinforcing fixed-choice usage and prohibiting personal content, credentials, links, conversations, or hidden reasoning in reported values.

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 states a specific action and resource: recording technical feedback as a problem, suggestion, or successful outcome using fixed choices. It is clearly distinct from sibling order/card/content tools, which do not cover feedback reporting.

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?

It gives explicit timing and constraints: use after communicating the outcome to the buyer, it is optional, and it is never required to buy a card. That is a clear when-to-use and when-not-to-use signal.

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

All Paddock Cards 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?