Bounty Engineer Agent Commerce

Quote a complete multi-tool API workload before buying credits

quote_premium_workload

Read-onlyIdempotent

Free quote for up to 20 tool/call rows under a hard total budget. Compares one shared-key package against pay-per-call pricing and recommends a prepaid package only when it covers all tools and costs less. Includes smaller and funding-only alternatives; does not buy or create invoices.

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": {
      "workload": "<workload>",
      "max_spend_usd": "<max_spend_usd>"
    },
    "name": "quote_premium_workload"
  }
}

Input Schema

Name	Required	Description	Default
`workload`	Yes	Buyer-declared recurring workload. Example: [{"tool":"funding-rates","calls":10000}]
`max_spend_usd`	Yes	Hard buyer-approved total budget in USD. The free quote does not authorize a charge

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 13, 2026

addedInput schema / properties / max_spend_usd / description

Added value: +"Hard buyer-approved total budget in USD. The free quote does not authorize a charge"

addedInput schema / properties / workload / description

Added value: +"Buyer-declared recurring workload. Example: [{\"tool\":\"funding-rates\",\"calls\":10000}]"

addedInput schema / properties / workload / items / properties / calls / description
```
Added value: +"Expected paid calls for this tool, not website visits"
```
addedInput schema / properties / workload / items / properties / tool / description
```
Added value: +"Tool id from list_products. Example: funding-rates"
```

AddedOct 8, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real substance beyond that: it is free, capped at 20 rows, compares shared-key vs pay-per-call, only recommends prepaid when it covers all tools and is cheaper, and includes smaller/funding-only alternatives.

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 tight sentences, front-loaded with the core offer and capped with the negative constraint. Every sentence carries information; only the closing clause mildly overlaps with the read-only annotation.

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 read-only quoting tool with no output schema, the description adequately conveys the comparison logic, the recommendation condition, and what the quote will not do. An agent has enough to invoke it correctly, though it does not describe the shape of the returned recommendation.

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% and both parameters carry their own descriptions with examples and bounds, so the schema does the heavy lifting. The description restates the row cap and budget concept but adds no syntax or format detail beyond what is already structured.

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 ('Free quote') and resource ('up to 20 tool/call rows'), and the multi-tool workload framing separates it from single-tool siblings like quote_instant_work. It does not explicitly name sibling tools, so the differentiation is implied by scope rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It establishes context ('before buying credits') and a boundary ('does not buy or create invoices'), which tells the agent this is a pre-purchase step. However, it never names which sibling quote tools to use instead for other scenarios, leaving selection to inference among the crowded quote_* family.

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

All Bounty Engineer Agent Commerce 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?