Skip to main content
Glama

Report a problem with a tool you bought

report_problem

Bought a tool (alone or in a bundle) and something is wrong with it? Send the slug, your purchase receipt (the X-Forge-Receipt token) and one sentence about the fault. Free. Forge's agents pick it up within the hour; a real fault is fixed, passes the same checks, and you download the new version free at /forge/packages/{slug}/update with your receipt. No money back through this tool.

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": {
      "slug": "<slug>",
      "receipt": "<receipt>",
      "problem": "<problem>"
    },
    "name": "report_problem"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
problemYesWhat is wrong, one sentence, 10-300 characters
receiptYesThe X-Forge-Receipt token from your purchase

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses cost (free), turnaround (agents pick it up within the hour), the outcome for a valid fault (fixed, re-checked, new version downloadable at /forge/packages/{slug}/update), and the exclusion of refunds. It does not say what happens if the report is judged not a real fault, or what confirmation the caller receives, which keeps it below a 5.

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?

Front-loaded with the triggering scenario, then the required inputs, then the outcome and the refund caveat — a sensible order with no filler sentences. There is minor redundancy between "Free" early and "you download the new version free" later, which costs it the top score.

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 three-parameter, no-output-schema, no-annotation mutation tool, the description covers the inputs, the cost, the processing timeline, and the resolution path, which is close to what an agent needs. The remaining gap is the response shape (whether a ticket or confirmation is returned) and the failure case for a rejected report.

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 67%, with the two descriptive gaps (problem length, receipt token identity) already documented in the schema. The description adds modest meaning — that the slug is the purchased tool's and that the receipt proves the purchase, and that "problem" should be one sentence — but it largely restates what the schema already conveys, so the baseline 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?

"Report a problem with a tool you bought" names a specific verb (report), resource (a problem with a purchased tool), and scope (purchased, alone or in a bundle). No sibling (buy_product, try_product, revise_order) could be confused with this one, and the title reinforces the same distinction.

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?

The opening question establishes the exact trigger condition — you bought a tool and something is wrong with it — and the closing line "No money back through this tool" sets an explicit boundary on expectations. It stops short of naming where refunds are actually handled, so the redirect is implied rather than routed to a named alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources