Skip to main content
Glama

select_work_request_proposal

Select a fresh-work proposal using the buyer signature. No ticket or payment is created; inspect whether the response contains a direct Work Ticket handoff or a separate protected inspection handoff. Never substitute direct checkout for protected funding. New fresh-work selections retain the exact verified message and buyer signature atomically with selection. Replays preserve the original proof. Older selections may lack the signed message; migration and replay do not reconstruct it. Public reads exclude these proofs; selections linked to direct Work Tickets can be read through the private Transaction Evidence export. Save the original message and signature locally. Selection authorizes no payment.

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": {
      "requestId": "<requestId>",
      "challengeId": "<challengeId>",
      "signature": "<signature>"
    },
    "name": "select_work_request_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYes
signatureYes
challengeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Added

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it states no ticket or payment is created, that 'Selection authorizes no payment,' that proofs are stored atomically, that replays preserve the original proof, that older selections may lack the signed message, and that proofs are excluded from public reads. Missing are auth requirements and failure behavior for an invalid signature, which keeps this short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded, but the remainder drifts across proof storage, migration replays, public read visibility, and the Transaction Evidence export, mixing durable caveats with low-frequency edge cases. Several sentences earn their place, but the block is denser than needed for an agent deciding whether and how to call it.

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 signature-gated mutation with no output schema and no annotations, the description covers consequences and proof handling well but leaves the prerequisite challenge workflow and the meaning of two required identifiers unexplained. An agent would still guess about inputs and response shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three required parameters. The description only clarifies that 'signature' is the buyer signature tied to a verified message; it never explains what requestId identifies or that challengeId is a selection challenge, so two of three parameters remain undocumented in both schema and prose.

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 concrete verb and resource: 'Select a fresh-work proposal using the buyer signature.' That distinguishes it from proposal-creation and completion siblings, but it never contrasts with the similarly named select_buyer_request_offer or explains what makes a proposal 'fresh-work,' so an agent must infer the boundary.

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: the challengeId parameter and 'using the buyer signature' hint that a selection challenge must precede this call, and 'Never substitute direct checkout for protected funding' is an operational constraint rather than a when-to-use rule. No explicit conditions or named alternatives for choosing this over sibling selection tools are given.

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