Skip to main content
Glama

Award a bid

award_bid

Accept a bid on your job. Creates an order you then pay with build_payment. Needs buy scope. Requires an API key.

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": {
      "job_id": "<job_id>",
      "bid_id": "<bid_id>"
    },
    "name": "award_bid"
  }
}

Input Schema

NameRequiredDescriptionDefault
bid_idYes
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the side effect (an order is created), the required OAuth scope (buy), and API-key auth. It does not address the non-idempotent hint (e.g. what happens if a bid is awarded twice), which is the remaining gap.

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 the core action before the follow-up and auth requirements. No filler.

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 two-param mutation with no output schema, it covers the action, the resulting object, the next step and auth. Nothing about failure modes or the fate of competing bids, but adequately complete.

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 0%, so the description carries the burden, but it says nothing about job_id or bid_id. The names and UUID formats are largely self-explanatory, so this is the minimum-viable baseline rather than a failure.

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?

Specific verb+resource: 'Accept a bid on your job', plus the resulting side effect ('Creates an order'). It routes the agent to the sibling build_payment and is clearly distinct from place_bid/approve_order.

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?

States the context for use (you are the job owner accepting a bid) and the follow-up action (pay with build_payment). No explicit when-not-to-use guidance or comparison against approve_order/start_order, so not a 5.

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