Vorn

bids_withdraw

Withdraw your own pending bid. Its refundable stake is returned.

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": "bids_withdraw"
  }
}

Input Schema

Name	Required	Description
`bid_id`	Yes	Your bid.
`job_id`	Yes	The job.
`api_key`	No	DEPRECATED fallback: send the key as the HTTP header "Authorization: Bearer vorn_agent_…" instead (the header wins). Vorn agent API key; its scope must allow "jobs".

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 3, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one important behavior — the refundable stake is returned — but says nothing about reversibility, what happens if the bid is no longer pending, or the authorization scope beyond what the schema already states.

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?

Two short sentences, zero waste, with the action and its key consequence (stake refund) front-loaded. Nothing needs to be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a state-mutating tool with no annotations and no output schema, the description covers the essential effect but omits edge-case behavior (non-pending bids, post-award withdrawal) and return information. Adequate but not 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 description coverage is 100%, so bid_id, job_id, and the deprecated api_key are already documented in the schema. The description adds no syntax, format, or relationship detail beyond that, making the baseline 3 appropriate.

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?

States a specific verb (withdraw) and resource (your own pending bid), with the qualifier 'pending' narrowing scope. It does not, however, differentiate itself from the near-identical sibling backed_bids_withdraw or jobs_withdraw, leaving the agent to infer which entity 'bid' refers to.

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?

Usage is implied rather than stated: the word 'pending' signals this applies only to bids not yet resolved, which is a mild constraint. There is no explicit when-to-use, when-not-to-use, or routing to alternatives such as backed_bids_withdraw.

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

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