Skip to main content
Glama

propose_work_request

Propose fresh work using an owned accepting worker capability. Direct proposals declare a seller-funded test budget. Explicit protected_inspection proposals use buyer-funded testing and a separate configured escrow; selection never pays. One current response per merchant; use revise_work_request_response to change it before selection.

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": {
      "capability": "<capability>",
      "deliverable": "<deliverable>",
      "priceUSDC": "<priceUSDC>",
      "deliveryDeadline": "<deliveryDeadline>",
      "testPurchaseBudgetUSDC": "<testPurchaseBudgetUSDC>",
      "testPurchasePayer": "<testPurchasePayer>",
      "note": "<note>",
      "requestId": "<requestId>"
    },
    "name": "propose_work_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesPublic untrusted text; at most 300 Unicode code points after trimming.
priceUSDCYes
requestIdYes
capabilityYes
inspectionNo
deliverableYesPublic untrusted text; at most 300 Unicode code points after trimming.
settlementModeNo
deliveryDeadlineYes
testPurchasePayerYes
testPurchaseBudgetUSDCYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / settlementMode / const
      Removed value: -"protected_inspection"
    • addedInput schema / properties / settlementMode / enum
      Added value: +[
      +  "direct_prepayment",
      +  "protected_inspection"
      +]
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Added

TDQS

A3.6/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 delivers real behavioral context: funding source per settlement mode, a 'separate configured escrow' for protected_inspection, the reassuring 'selection never pays', and the one-live-proposal-per-merchant limit. It omits auth/permission requirements, reversibility, and what happens on validation failure, so it is strong but not exhaustive for a money-touching mutation.

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?

Four sentences, front-loaded with purpose before the settlement-mode distinctions and the revise pointer. Dense but every sentence carries information; minor cost is the compressed jargon that makes the first sentence slower to parse than necessary.

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 10-parameter, nested, financially binding tool with no annotations and no output schema, the description covers the highest-stakes decisions (which settlement mode, who funds testing, no payment on selection, one live proposal) but leaves the entire inspection sub-object, deadlines, and post-submission state unexplained.

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 only 20% across 10 parameters, so the description must compensate and largely does not. It clarifies the settlementMode/payer/budget relationship implicitly, but says nothing about capability, requestId, note, deliverable, deliveryDeadline, priceUSDC, or any field of the nested 'inspection' object (targetUrl, paymentRecipient, maxTestAmountAtomic, maxPaidAttempts) — the most error-prone part of the schema.

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 and resource ('Propose fresh work') and immediately narrows the mechanism ('using an owned accepting worker capability'), plus splits the two settlement paths. It is distinguishable from siblings like revise_work_request_response and propose_buyer_request_offer, though the phrases 'fresh work' and 'owned accepting worker capability' are internal jargon an agent must already know.

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?

Gives explicit routing for the main branch point: 'Direct proposals' vs 'Explicit protected_inspection proposals', and names the alternative 'use revise_work_request_response to change it before selection'. It also states the uniqueness constraint ('One current response per merchant'). It stops short of saying when to prefer this tool over propose_buyer_request_offer or what preconditions (an owned capability) must hold.

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