Business Frameworks

Business Frameworks: quote the bundle for a task

bf_resolve

Read-onlyIdempotent

Quotes the minimal set of nodes that answers a broad task — a decision bundle, a market (chain) bundle or a cross bundle — with its price — one flat price, USD 0.05, with or without its scale band — stated before anything is paid. Deterministic and free: a named bundle or decision wins, then the input fields sent, then the authored patterns of the question; on ambiguity it returns candidates with their task lines, and with no match the task lines to choose from. Call it when the user's question takes more than one node (a whole decision with its context, a supply chain read, a shock traced to a seat), passing the question, revenue_usd and chain_position when known; then buy the quote with bf_read_bundle or read nodes one at a time with bf_read_node. Do not use it for a single term or a single rule, which bf_catalogue and bf_read_node answer more cheaply, and do not treat a quote as an answer: it names the nodes and the price, nothing more.

Input Schema

Name	Required	Description
`bundle`	No	A bundle id from a task line, when the caller already knows which.
`inputs`	No	The figures already in hand, by field name; the resolver reads the names, not the values.
`decision`	No	A decision path when the task is one decision, e.g. "cash-flow/decide/runway".
`question`	No	The task in the user's words (up to 2,000 characters).
`revenue_usd`	No	Annual revenue in US dollars, to pick the scale band.
`chain_position`	No	Where the business sits on the chain being read: binding_upstream, binding_downstream, at_binding or unknown.

Output Schema

Name	Required	Description	Default
`by`	No
`how`	No
`match`	No
`tasks`	No
`access`	No
`bundle`	No
`candidates`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "description": "A quote: match (single, candidates, none, out_of_scope), by (what decided it), bundle {id, task, nodes, price_usd — a flat USD 0.05 — tokens, url, band} or candidates/tasks to choose from; the access sentence.",
+  "properties": {
+    "access": {
+      "type": "string"
+    },
+    "bundle": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "by": {
+      "type": "string"
+    },
+    "candidates": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "how": {
+      "type": "string"
+    },
+    "match": {
+      "type": "string"
+    },
+    "tasks": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedOct 12, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses the pricing behavior, that the quote is free and deterministic, the resolution precedence, ambiguity handling, and no-match behavior. It also clarifies that a quote names nodes and price but is not itself an answer.

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?

The description is dense but front-loaded and every sentence carries operational value: purpose, behavior, invocation conditions, alternatives, and what a quote is not. There is no filler or redundant restatement of the schema.

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?

With annotations, a full input schema, and an output schema already present, the description completes the picture by explaining routing, pricing, determinism, ambiguity handling, and follow-up tools. An agent has enough information to decide when and how to invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already documents all six parameters, the description adds meaningful resolution semantics: a named bundle or decision wins, then the input fields sent, then the authored patterns of the question. It also tells the caller to pass question, revenue_usd, and chain_position when known.

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 gives a specific verb and resource: it quotes the minimal set of nodes for a broad task, covering decision, market/chain, and cross bundles. It also distinguishes this tool from bf_catalogue and bf_read_node by naming what those are better for, so an agent can route between them without opening schemas.

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

Usage Guidelines5/5

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

It explicitly states when to call it: when the user's question takes more than one node. It also states the alternatives and exclusions: use bf_catalogue or bf_read_node for a single term or rule, and use bf_read_bundle or bf_read_node after receiving the quote.

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

All Business Frameworks tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.