FeedbackQueue

create_order

Order a paid human review of a web app. Returns a Stripe Checkout link that a person must open and pay in the browser; the order stays in draft until then. Never pay on the user's behalf.

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": {
      "product_url": "<product_url>",
      "tier": "<tier>",
      "what_to_test": "<what_to_test>"
    },
    "name": "create_order"
  }
}

Input Schema

Name	Required	Description
`tier`	Yes	standard: 1 reviewer, $29. deep: 3 reviewers, $79.
`product_url`	Yes	Public URL of the app, starting with https://
`product_name`	No	Optional. Defaults to the URL's domain
`what_to_test`	Yes	What the reviewer should focus on, in a sentence or two
`test_credentials`	No	Optional login for a test account. Encrypted and shown only to the assigned reviewer

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.2/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 real work: it discloses the return value (a Stripe Checkout link), the state machine (order stays in draft until payment), the human-in-the-loop requirement, and an explicit agent constraint against paying. It doesn't cover link expiry, idempotency of repeated calls, or whether unpaid drafts linger.

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 short sentences, front-loaded with purpose, then the return/state behavior, then the constraint. No filler or restatement of the title.

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?

No output schema exists, and the description compensates by describing the returned Checkout link and the draft state. What's missing is minor lifecycle detail such as link expiry or the recommended follow-up call, but an agent has enough to invoke this 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%, so tier pricing, URL format, optional name default, and credential encryption are already documented in the schema. The description adds no parameter-level meaning beyond that, so 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?

States a specific verb and resource: 'Order a paid human review of a web app.' The transactional nature (paid, human, Stripe checkout) immediately separates it from the read-oriented siblings get_order_status, get_fix_brief, and list_orders.

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?

Establishes the key precondition that a person must open the link and pay in the browser, and forbids the agent from paying on the user's behalf. It doesn't explicitly route the agent to get_order_status afterward or state when not to create an order, so it stops short of full when/when-not guidance.

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

All FeedbackQueue 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?