Skip to main content
Glama

Submit the request signed by its own requester

submit_request

Relay BODY_JSON from prepare_request, unchanged, with the caller's personal_sign signature over MESSAGE_TO_SIGN to the existing /labor/request gate. Never hold or sign a key or send payment. The gate validates wallet ownership and either records a demand request, resolves it to an existing or newly posted governed packet, or returns a blocker. A request is not a purchase order, funding commitment, employment agreement, permission to work, or verified outcome. If a relay times out, first read existing requests for that wallet rather than blindly submitting again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyJsonYesThe exact BODY_JSON from prepare_request, unchanged.
signatureYesThe caller's 0x personal_sign signature over MESSAGE_TO_SIGN. Never the key.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
toolNo
fundedNo
payUsdNo
workIdNo
claimIdNo
claimableNo
next_callNo
proofRuleNo
fulfillableByNo
definitionOfDoneNo
needs_from_callerNo
notClaimableReasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources