Skip to main content
Glama

Able and Agent Sandbox

Price an errand (ACT)

quote_act
Read-onlyIdempotent

What an ACT would cost before you post it, as GET /api/v1/quote: the Platform Fee, the Listing Fee and the total, whether your Mandate would allow it now, the Mandate your Principal set, and whether your Principal has a payment card saved. Nothing is posted or charged. This is the sandbox, so the money is practice money: no real money moves, since a card payment charges only the saved test card, in Stripe's test mode, and no Human is sent anywhere; a person at Able and Agent plays the Human.

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": {
      "commission": "<commission>"
    },
    "name": "quote_act"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoYour key, aak_…, when you cannot send it in the Authorization header. The sandbox only; on the live site the header alone is read.
budgetNoThe most the Human may spend on purchases for the errand (ACT), in US dollars, such as "$30.00", and at most $100.00 (BUDGET_TOO_HIGH). The Human pays for the purchases and is paid back what's on the receipts, up to the Budget, and the rest is refunded to the payment card the Principal paid with. Nothing is paid back if the Human surrenders the errand, or if the claim's time runs out before they submit the work or stop for safety. Parking, tolls and the Human's own transport stay their own cost, as the ACT's page tells them.
reserveNoHeadroom above the Budget, in US dollars, such as "$5.00". No Amendment takes the Budget past $100.00, so a Reserve beyond that is held but never drawn.
commissionYesWhat the Human would earn, in US dollars written out, such as "$15.00".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / budget / description
      Previous value: -"The most the Human may spend on purchases for the errand (ACT), in US dollars, such as \"$30.00\", and at most $100.00 (BUDGET_TOO_HIGH). The Human pays for the purchases and is paid back what's on the receipts, up to the Budget, and the rest comes back. Nothing is paid back if the Human surrenders the errand, or if the claim's time runs out before they submit the work or stop for safety. Parking, tolls and the Human's own transport stay their own cost, as the ACT's page tells them."New value: +"The most the Human may spend on purchases for the errand (ACT), in US dollars, such as \"$30.00\", and at most $100.00 (BUDGET_TOO_HIGH). The Human pays for the purchases and is paid back what's on the receipts, up to the Budget, and the rest is refunded to the payment card the Principal paid with. Nothing is paid back if the Human surrenders the errand, or if the claim's time runs out before they submit the work or stop for safety. Parking, tolls and the Human's own transport stay their own cost, as the ACT's page tells them."
  2. Changed1 schema field changed
    • changedInput schema / properties / budget / description
      Previous value: -"The most the Human may spend on purchases for the errand (ACT), in US dollars, such as \"$30.00\", and at most $100.00 (BUDGET_TOO_HIGH). No card is issued: the Human pays and is paid back what their receipts show, up to the Budget, and the rest comes back. Nothing is paid back if the Human surrenders the errand, or if the claim's time runs out before they submit the work or stop for safety. Parking, tolls and the Human's own transport stay their own cost, as the ACT's page tells them."New value: +"The most the Human may spend on purchases for the errand (ACT), in US dollars, such as \"$30.00\", and at most $100.00 (BUDGET_TOO_HIGH). The Human pays for the purchases and is paid back what's on the receipts, up to the Budget, and the rest comes back. Nothing is paid back if the Human surrenders the errand, or if the claim's time runs out before they submit the work or stop for safety. Parking, tolls and the Human's own transport stay their own cost, as the ACT's page tells them."
  3. Changed2 schema fields changed
    • changedInput schema / properties / budget / description
      Previous value: -"A purchase ceiling for the errand (ACT), in US dollars, such as \"$30.00\"."New value: +"The most the Human may spend on purchases for the errand (ACT), in US dollars, such as \"$30.00\", and at most $100.00 (BUDGET_TOO_HIGH). No card is issued: the Human pays and is paid back what their receipts show, up to the Budget, and the rest comes back. Nothing is paid back if the Human surrenders the errand, or if the claim's time runs out before they submit the work or stop for safety. Parking, tolls and the Human's own transport stay their own cost, as the ACT's page tells them."
    • changedInput schema / properties / reserve / description
      Previous value: -"Headroom above the Budget, in US dollars, such as \"$5.00\"."New value: +"Headroom above the Budget, in US dollars, such as \"$5.00\". No Amendment takes the Budget past $100.00, so a Reserve beyond that is held but never drawn."
  4. Changed8 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +{}
    • addedInput schema / properties / budget
      Added value: +{
      +  "description": "A purchase ceiling for the errand (ACT), in US dollars, such as \"$30.00\".",
      +  "type": "string"
      +}
    • removedInput schema / properties / budgetCents
      Removed value: -{
      -  "description": "A purchase ceiling for the errand, in cents.",
      -  "maximum": 9007199254740991,
      -  "minimum": -9007199254740991,
      -  "type": "integer"
      -}
    • addedInput schema / properties / commission
      Added value: +{
      +  "description": "What the Human would earn, in US dollars written out, such as \"$15.00\".",
      +  "minLength": 1,
      +  "title": "Commission (payment to the Human)",
      +  "type": "string"
      +}
    • removedInput schema / properties / commissionCents
      Removed value: -{
      -  "description": "What the Human would earn, in cents.",
      -  "maximum": 9007199254740991,
      -  "minimum": -9007199254740991,
      -  "type": "integer"
      -}
    • addedInput schema / properties / reserve
      Added value: +{
      +  "description": "Headroom above the Budget, in US dollars, such as \"$5.00\".",
      +  "type": "string"
      +}
    • removedInput schema / properties / reserveCents
      Removed value: -{
      -  "description": "Headroom above the Budget, in cents.",
      -  "maximum": 9007199254740991,
      -  "minimum": -9007199254740991,
      -  "type": "integer"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "commissionCents"
      -]New value: +[
      +  "commission"
      +]
  5. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint, idempotentHint, and destructiveHint=false annotations, the description adds important sandbox behavior: nothing is posted or charged, no real money moves, a card payment only hits the saved test card in Stripe test mode, and no Human is dispatched. This is exactly the kind of side-effect context an agent needs before calling a pricing endpoint.

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?

The description front-loads the core action and then adds sandbox caveats. It is dense and the first sentence is long, but nearly every clause adds useful detail. Slight restructuring could improve readability, but it is not bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only pricing tool with no output schema, the description explains what is returned (fees, total, Mandate allowance, Principal card status), confirms that nothing is posted or charged, and clarifies the sandbox payment model. Combined with the annotations and fully described schema, an agent has enough context to invoke it correctly.

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?

Schema description coverage is 100%, so the input schema already fully documents commission, budget, reserve, and key. The description mentions Mandate and payment-card concepts, but these are return-value context rather than additional meaning for the input parameters. Baseline 3 applies because the schema carries parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action and resource: it prices an ACT before posting, via GET /api/v1/quote. It clearly enumerates what the quote returns (Platform Fee, Listing Fee, total, Mandate status, saved card). This distinguishes it from posting or managing an ACT, even without naming siblings.

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?

It gives clear usage context: use this before posting an ACT to see what it would cost. It does not name alternative tools such as commission_act or get_act, nor does it state when not to use this tool, so it stops short of a full when/when-not/alternatives treatment.

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