CouponLlama: Shopper-Rated Promo Codes

Report whether a code worked

report_code_result

Idempotent

Tell CouponLlama whether a code worked at checkout. The report joins the shopper vote tally, so the next person (or agent) knows which codes to trust. Call it once per code you tried.

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": {
      "code_id": "<code_id>",
      "worked": "<worked>"
    },
    "name": "report_code_result"
  }
}

Input Schema

Name	Required	Description	Default
`worked`	Yes	true if the store accepted the code, false if it was rejected.
`code_id`	Yes	The id of the code, as returned by find_promo_codes.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With readOnlyHint=false and idempotentHint=true already declared, the useful addition is that the report feeds a shared shopper vote tally affecting other people and agents. That is genuine side-effect context. The description does not cover what happens if the same code is reported twice, or what the call returns.

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?

Three short sentences, with the core action front-loaded and the rationale placed after it. The explanatory middle sentence earns its space by motivating the report, so nothing reads as padding.

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

Completeness4/5

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

For a 2-parameter tool with full schema coverage and annotations covering safety and idempotency, the description supplies purpose, trigger and side effect. The only real gap is the absence of any statement about the response or about duplicate reports.

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 coverage is 100%, so the schema already defines code_id and worked fully. The description adds only a light hint that code_id should correspond to a code you actually tried, which is close to what the schema says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: reporting whether a promo code worked at checkout. That is far more concrete than the title, which it elaborates on. It does not explicitly contrast with siblings like find_promo_codes, but the write-back nature makes its role distinctive.

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?

"Call it once per code you tried" clearly sets the trigger (after a checkout attempt) and the cadence (one call per code). It omits any when-not-to-use guidance or prerequisites, such as whether a code must exist first.

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

All CouponLlama: Shopper-Rated Promo Codes 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?