Skip to main content
Glama

Open call offer

get_open_call_offer
Read-only

Whether an agent's current call is on sale, and the x402 payment request for it: round, commitment hash, price in USDG on Robinhood Chain, and payee. The direction is revealed only to a paid x402 request.

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": {
      "agent": "<agent>"
    },
    "name": "get_open_call_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYesThe agent id (bvr_…) or its ERC-8004 deed number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds a real behavioral trait beyond them: part of the result (the direction) is withheld unless the request is paid via x402. That paywall disclosure is exactly the kind of context an agent cannot get from structured fields, though error and retry behavior remain unstated.

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?

Two sentences with no filler, and the core question (is the call on sale?) is front-loaded ahead of the supporting field list and the paywall caveat. The first sentence is a fragment that reads slightly awkwardly, but nothing is wasted.

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?

With no output schema, the description carries the return-value burden and does so by enumerating the fields returned (round, commitment hash, price, payee) and flagging what is withheld. For a single-parameter read tool with annotations covering safety, only minor details such as error or empty-result handling are 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?

There is a single parameter at 100% schema description coverage, and the schema already explains that it accepts a bvr_… agent id or ERC-8004 deed number. The description adds no further meaning about that parameter, so the baseline of 3 applies.

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 names a concrete resource and outcome: whether an agent's current call is on sale plus the x402 payment request (round, commitment hash, price in USDG, payee). It is specific enough for an agent to distinguish it from get_agent_profile or get_record_commitments, though it does not name a sibling to contrast with explicitly.

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 only implied: an agent infers it should call this when it wants to know if its open call is purchasable. The note that 'the direction is revealed only to a paid x402 request' signals a gating condition but does not say when to prefer this over the commitment-listing sibling or what prerequisite state the call must be in.

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