Skip to main content
Glama

Able and Agent Sandbox

by com.ableandagent
OverviewDiscussionsAdmin

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 and your Principal's balance would allow it now, and the Mandate your Principal set. Nothing is posted or charged. This is the sandbox, so the money is practice money: no real money moves, no card is charged, and no Human is sent anywhere; a person at Able and Agent plays the Human.

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). 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.
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. 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."
  2. 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"
+]
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, but the description adds real context on top: nothing is posted or charged, the sandbox uses practice money, no card is charged, and a person at Able and Agent plays the Human. That sandbox framing is not derivable from annotations and materially affects how an agent interprets the result.

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

Conciseness5/5

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

Purpose and endpoint are front-loaded in the first clause, the returned values follow, and the safety/sandbox caveat closes it. The 'nothing is posted' and 'no real money moves' clauses are slightly overlapping but each reinforces a distinct concern (side effects vs. financial risk).

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?

There is no output schema, and the description compensates by enumerating every returned figure (fees, total, eligibility flags, the mandate itself). Combined with the explicit no-side-effect statement, an agent has everything needed to call it and interpret the response.

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% and the parameter descriptions are unusually rich (budget caps, reserve headroom, key/header fallback), so the schema already carries the semantic load. The description adds no parameter-level detail of its own beyond referencing Mandate and Principal's balance, so baseline 3 applies.

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?

Names a specific verb-and-resource ('what an ACT would cost before you post it'), gives the backing endpoint GET /api/v1/quote, and enumerates the exact outputs (Platform Fee, Listing Fee, total, mandate/balance checks). This clearly separates it from commission_act (which actually posts) and get_act (which reads an existing errand).

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?

'before you post it' establishes the lifecycle position and makes the use case obvious to an agent preparing an errand. It stops short of explicitly naming commission_act as the follow-up alternative or stating when not to call it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Able and Agent Sandbox toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources