InfraPulse

Quote InfraPulse work

quote

Read-onlyIdempotent

Get a deterministic price quote before authorization or execution. This does not reserve credits or run provider work.

Input Schema

Name	Required	Description	Default
`task`	No
`sector`	No
`payload`	No
`sectors`	No
`agent_id`	No
`metadata`	No
`user_tier`	No
`work_type`	No
`capability`	No
`request_id`	No
`cross_sector`	No
`policy_profile`	No
`data_boundaries`	No
`estimated_units`	No
`receipt_required`	No
`providers_allowed`	No
`compliance_profile`	No
`budget_limit_credits`	No
`execution_constraints`	No

Output Schema

Name	Required	Description	Default
`ok`	No
`data`	No
`error`	No
`intent`	No
`status`	No
`receipt`	No
`success`	No
`request_id`	No
`next_action`	No
`operation_id`	No
`requires_human`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedNov 7, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "task"
+    ]
+  },
+  {
+    "required": [
+      "payload"
+    ]
+  }
+]

addedInput schema / properties / budget_limit_credits

Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / capability
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / compliance_profile
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / cross_sector
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / properties / data_boundaries
```
Added value: +{
+  "type": "object"
+}
```

addedInput schema / properties / estimated_units

Added value: +{
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / execution_constraints
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / metadata
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / payload / additionalProperties
```
Added value: +false
```

addedInput schema / properties / payload / properties

Added value: +{
+  "budget_limit_credits": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "capability": {
+    "type": "string"
+  },
+  "compliance_profile": {
+    "type": "string"
+  },
+  "cross_sector": {
+    "type": "boolean"
+  },
+  "data_boundaries": {
+    "type": "object"
+  },
+  "estimated_units": {
+    "minimum": 1,
+    "type": "integer"
+  },
+  "execution_constraints": {
+    "type": "object"
+  },
+  "metadata": {
+    "type": "object"
+  },
+  "policy_profile": {
+    "type": "string"
+  },
+  "providers_allowed": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "receipt_required": {
+    "type": "boolean"
+  },
+  "sector": {
+    "type": "string"
+  },
+  "sectors": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "task": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "user_tier": {
+    "type": "string"
+  },
+  "work_type": {
+    "type": "string"
+  }
+}

addedInput schema / properties / payload / required
```
Added value: +[
+  "task"
+]
```
addedInput schema / properties / policy_profile
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / providers_allowed

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / receipt_required
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / request_id

Added value: +{
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / sector
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / sectors

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / task

Added value: +{
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / user_tier
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / work_type
```
Added value: +{
+  "type": "string"
+}
```

First observedSep 1, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally. The description adds real value by clarifying that no credits are reserved and no provider work runs — the main thing an agent might fear about a pricing call. However, it says nothing about quote validity window, determinism inputs, or how the quoted price relates to the eventual authorization amount.

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?

Two short sentences, zero filler, with the primary purpose front-loaded and the negative side-effect clause immediately after. Nothing is wasted.

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?

This is a high-complexity tool with nested objects, a dual input shape, and 19 undocumented parameters, and the description does not address any of it. The output schema means return values need not be explained, but the input surface and quoting behavior are left almost entirely unexplained for a tool this complex.

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?

With 19 parameters and 0% schema description coverage, the description carries the full burden and provides nothing — not even what "task" or "sector" mean, nor the role of budget_limit_credits, policy_profile, providers_allowed, or execution_constraints in shaping the price. It also fails to explain the two accepted invocation shapes (flat task vs. nested payload) allowed by the anyOf.

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 verb and resource ("Get a deterministic price quote") and situates it in the pipeline relative to authorization and execution, which maps onto the authorize and execute siblings. It stops short of naming those tools directly, so the differentiation is implied rather than explicit.

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 clear timing guidance: call this before authorization or execution. That is a genuine ordering constraint an agent needs. It does not say what to do if the quote is rejected, stale, or when a quote is unnecessary, so there are no explicit exclusions.

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

All InfraPulse tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?