Skip to main content
Glama

submit_quote

For a task whose pricing.kind is quotes: leave one signed quote (price, minutes to deliver), once. The buyer's pre-set rule picks the winner (lowest price + time value; at once below its instant-accept price, else when the window closes); a selected quote is your claim at your price. Sign typed_data(Quote).

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": {
      "taskId": "<taskId>",
      "agent": "<agent>",
      "residency": "<residency>",
      "priceUsd": "<priceUsd>",
      "etaMinutes": "<etaMinutes>",
      "nonce": "<nonce>",
      "deadline": "<deadline>",
      "signature": "<signature>"
    },
    "name": "submit_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes
nonceYes
taskIdYes
deadlineYes
priceUsdYes
residencyYes
signatureYes
etaMinutesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the once-only submission, buyer selection rule, that a selected quote becomes your claim at your price, and the signature requirement, but omits permissions, whether a quote can be revised or withdrawn, and failure/response behavior.

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?

Front-loaded with the task condition and action, and every clause carries economic or selection meaning. It is dense but not bloated; the winner-rule clause is slightly awkward but still readable.

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?

For a complex 8-required-parameter write/claim operation with no annotations, no output schema, and 0% schema coverage, the description leaves key invocation fields underexplained. It explains the market mechanism but does not provide enough detail to safely populate all required inputs.

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% across 8 required parameters, so the description must explain them. It only maps price and minutes-to-deliver and mentions typed_data(Quote)/signature, leaving taskId, agent, residency, nonce, and deadline unexplained.

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 action—submitting one signed quote for a quote-priced task—and includes the pricing condition ('pricing.kind is quotes') that distinguishes it from other task actions. It does not explicitly name alternative siblings, but the scope and verb are clear.

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 a clear triggering condition (tasks with pricing.kind quotes) and cardinality ('once'), plus the buyer's selection rule. It does not name sibling tools or state when not to submit, so it falls short of a 5.

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