Skip to main content
Glama
Sign In

Able and Agent

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.

Input Schema

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

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real context: what the response contains and the explicit reassurance that no post or charge occurs. It does not cover failure modes such as BUDGET_TOO_HIGH (left to the schema) or rate limits, keeping it out of the top band.

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?

A single front-loaded sentence that leads with the cost-preview purpose and ends with the no-side-effect guarantee. It is dense with domain jargon ('Mandate', 'Principal') and could be split for readability, but nothing is wasted.

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

Completeness4/5

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

With no output schema, the description carries the burden of explaining returns and does so well by listing the fee components and the mandate/balance check. It is nearly complete for a read-only pricing call, missing only error expectations already covered by the schema.

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 each parameter is thoroughly documented there, including the $100 budget cap and reserve behavior. The description adds no parameter meaning beyond what the schema already provides, so the 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?

States a specific verb and resource ('what an ACT would cost before you post it'), names the underlying endpoint (GET /api/v1/quote), and enumerates exactly what comes back: Platform Fee, Listing Fee, total, mandate/balance approval, and the Mandate. The 'before you post it' framing separates it cleanly from commission_act.

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?

The phrase 'before you post it' and 'Nothing is posted or charged' clearly signal this is the preview step preceding posting, which implicitly routes the agent away from commission_act. It never names the alternative sibling or states when quoting is unnecessary, so it stops short of explicit when/when-not guidance.

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 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