Locus

Estimate cost

estimate_cost

Quote a costly or sensitive call with an optional hard cap; pass inputs in body.

Input Schema

TableJSON Schema

Name	Required	Description
`args`	No	Alias for body; must match body when both are provided.
`body`	No	Intended body; required for variable pricing.
`slug`	No	provider/endpoint, or use the pair below.
`endpoint`	No	Endpoint slug.
`provider`	No	Provider slug.
`idempotency_key`	No	Key shared with execute; generated if omitted.
`expires_in_seconds`	No	Lifetime seconds: default 120, range 30-600.
`max_charge_credits`	No	Optional positive decimal hard charge ceiling, as a string.
`preflight_external_quote`	No	Probe a live x402 quote without paying.

Output Schema

TableJSON Schema

Name	Required	Description
`slug`	No	provider/endpoint slug.
`message`	No	Human-readable quote outcome.
`executable_quote`	No	True when approval_token is included.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 17, 2026

addedInput schema / description

Added value: +"Provide exactly one endpoint selector: slug, or provider plus endpoint."

removedInput schema / oneOf

Removed value: -[
-  {
-    "properties": {
-      "slug": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "slug"
-    ]
-  },
-  {
-    "properties": {
-      "endpoint": {
-        "type": "string"
-      },
-      "provider": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "provider",
-      "endpoint"
-    ]
-  }
-]

addedInput schema / properties / args / description

Added value: +"Alias for body; must match body when both are provided."

changedInput schema / properties / max_charge_credits / description

Previous value: -"Optional hard charge ceiling."New value: +"Optional positive decimal hard charge ceiling, as a string."

addedInput schema / properties / max_charge_credits / maxLength
```
Added value: +100
```
addedInput schema / properties / max_charge_credits / minLength
```
Added value: +1
```

removedInput schema / properties / max_charge_credits / oneOf

Removed value: -[
-  {
-    "maxLength": 100,
-    "minLength": 1,
-    "type": "string"
-  },
-  {
-    "exclusiveMinimum": 0,
-    "type": "number"
-  }
-]

addedInput schema / properties / max_charge_credits / type
```
Added value: +"string"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "executable_quote": {
+      "description": "True when approval_token is included.",
+      "type": "boolean"
+    },
+    "message": {
+      "description": "Human-readable quote outcome.",
+      "type": "string"
+    },
+    "slug": {
+      "description": "provider/endpoint slug.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 15, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The description adds the key behavior of quoting with an optional hard cap and notes that inputs go in the body. However, given readOnlyHint is false, it does not disclose whether creating a quote has side effects or how it relates to execute.

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?

One front-loaded sentence, no filler. 'Quote a costly or sensitive call' captures purpose first, followed by the hard-cap option and body-input instruction.

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 9-parameter tool with no required params, this description is too thin. It omits the crucial pre-execution relationship with execute, side effects, and endpoint selection expectations; the rich schema and output schema do not compensate for the missing usage context.

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 coverage is 100% and every parameter has a description, so the schema already handles parameter semantics. The description's 'pass inputs in body' adds a mild usage hint, but it does not provide substantive meaning beyond the structured fields.

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?

The description uses a specific verb 'Quote' and defines the resource as 'a costly or sensitive call', which makes the primary purpose clear. It also mentions the optional hard cap, but it does not explicitly contrast with siblings like execute or cancel_cost_approval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance is provided. The phrase 'costly or sensitive call' implies a condition, but there is no explicit instruction to invoke this before execute or any mention of alternatives.

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

All Locus tools Inspect

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.