Skip to main content
Glama
Sign In

Bounty Engineer Agent Commerce

by io.github.gatoprd
OverviewDiscussionsAdmin

Check your input and exact premium delivery contract for free

quote_premium_delivery
Read-onlyIdempotent

Validate actual caller-supplied Command Center or Control Tower input before authorizing an expensive analysis. Returns input hash, counts, deliverable list, posted price and a cheaper standalone alternative when one workspace suffices. Does not return the paid analysis, verify receipts on chain, sign or transfer funds.

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": {
      "tool": "<tool>",
      "input": "<input>",
      "max_spend_usd": "<max_spend_usd>"
    },
    "name": "quote_premium_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesExact premium tool id; Command Center is for one workspace, Tower for genuine cross-workspace needs
inputYesReal buyer-owned analysis inputs; never send wallet secrets, private keys or credentials
max_spend_usdYesMaximum buyer-approved USD budget; preview never charges

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / input / description
      Added value: +"Real buyer-owned analysis inputs; never send wallet secrets, private keys or credentials"
    • addedInput schema / properties / max_spend_usd / description
      Added value: +"Maximum buyer-approved USD budget; preview never charges"
    • addedInput schema / properties / tool / description
      Added value: +"Exact premium tool id; Command Center is for one workspace, Tower for genuine cross-workspace needs"
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes further: it enumerates the exact payload (input hash, counts, deliverable list, posted price, cheaper standalone alternative) and explicitly bounds what the tool will NOT do. For a preview tool with no output schema, this is exactly the missing context an agent needs.

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 sentences, front-loaded with the purpose, then the return contents, then the negative scope. Every sentence carries distinct information and none repeats the title or annotations.

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 a nested-object input, an enum, no output schema and read-only annotations, the description supplies the two things structured fields cannot: the preview-versus-execution framing and an explicit list of what is and is not returned. Nothing needed to invoke it correctly is missing.

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% and each parameter is documented in the schema itself, so the baseline is 3. The description's 'when one workspace suffices' adds a little meaning to the tool enum choice, but it does not add syntax or format detail beyond what the schema already provides.

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 — validate caller-supplied Command Center/Control Tower input and return a delivery quote — so the tool is distinguishable from the paid execution tool it precedes. It does not name a sibling such as execute_paid_product explicitly, so it falls just short of full sibling differentiation.

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?

It gives a clear context: use this to validate real buyer inputs 'before authorizing an expensive analysis.' Exclusions are present in the negative-scope sentence (does not return the paid analysis, verify receipts, sign or transfer funds), though no alternative tool is named for that follow-up step.

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 toolsInspect
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