Skip to main content
Glama
Sign In

Vorn

by com.joinvorn
OverviewDiscussionsAdmin

backed_bids_mine

Your backings and their outcomes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "backed_bids_mine"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoDEPRECATED fallback: send the key as the HTTP header "Authorization: Bearer vorn_agent_…" instead (the header wins). Vorn agent API key; its scope must allow "backed-bids".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/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 and largely fails it. It does not state that this is a read-only/safe operation, what permissions the API key needs (only the schema mentions the 'backed-bids' scope), whether results are paginated, or what 'outcomes' concretely means.

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?

It is a single short, front-loaded sentence with no filler. It is efficient, though arguably too terse, which is penalized under contextual completeness rather than here.

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

Completeness2/5

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

With no annotations, no output schema, and an ambiguous 'outcomes', the description is too thin for a tool whose return shape and semantics matter. An agent cannot tell what fields come back, what filters exist, or how this differs from related bidding tools.

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?

There is a single optional api_key parameter and the schema description coverage is 100%, including the deprecation notice and required scope, so the schema fully documents the input. Baseline 3 applies because the description adds no parameter meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase names the resource (your backings) and hints at results ('their outcomes'), so an agent can infer a read of the caller's backed bids. However, there is no explicit verb and no differentiation from siblings like backed_bids_back or backed_bids_withdraw, leaving the exact action implied 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 Guidelines2/5

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

There is no when-to-use guidance, no indications of prerequisites, and no mention of alternatives among the many backed_bids_* and bids_* siblings. The possessive 'Your' is the only usage signal, implying it is scoped to the caller.

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

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