Business Frameworks

Business Frameworks: read a quoted bundle

bf_read_bundle

Read-only

Returns the nodes of one bundle in order — the central node full, the supporting nodes terse — with citations and a cite-as line per node, on one settlement at the quoted price (a flat $0.05 for every bundle, band included; USDC on Base over x402). Pass the bundle id from bf_resolve or bf_catalogue, and a band to add the scale band for the business's revenue. Call it after bf_resolve has quoted the bundle and the user accepts the price; the quote's url is the same resource over HTTP. Do not call it to browse: the quote already lists the nodes and the price, and a narrow question is cheaper node by node through bf_read_node.

Input Schema

Name	Required	Description	Default
`band`	No	A scale band to add, by slug ("1-5m") or label ("$1–5M"); omit for the bundle without a band.
`bundle`	Yes	Bundle id from bf_resolve or bf_catalogue, e.g. "runway"; the quote url is accepted too.

Output Schema

Name	Required	Description	Default
`id`	No
`task`	No
`nodes`	No
`handle`	No
`cite_as`	No
`price_usd`	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": "The bundle's nodes in order — the central node full, the rest terse — each with its text, variant, role and cite_as; one settlement at the quoted flat price.",
+  "properties": {
+    "cite_as": {
+      "type": "string"
+    },
+    "handle": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "nodes": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "cite_as": {
+            "type": "string"
+          },
+          "handle": {
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          },
+          "text": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "variant": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "price_usd": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "task": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 12, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Adds substantial behavior beyond the read-only annotations: one settlement at a flat $0.05 per bundle, USDC on Base over x402, the quote URL is the same resource over HTTP, and the return is ordered with central versus supporting node detail. These are concrete operational traits an agent needs before invoking a paid read tool.

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?

Front-loads the return shape in the first sentence, then pricing and prerequisites, then exclusions. Every sentence carries distinct operational information; nothing is filler given the paid, gated nature of the tool.

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?

Even with an output schema, the description covers what is returned at a high level, the payment and quote prerequisite, the bundle/band inputs, and the sibling alternative for browsing or narrow reads. An agent has enough context to decide whether and how to call it.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already defines both parameters. The description still adds useful context: where to get the bundle id, that the quote URL is accepted, and that band adds the scale band for the business's revenue. It does not add format examples beyond the schema, so it is strong but not fully additive.

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: returns the ordered nodes of one bundle, with central node full and supporting nodes terse. It also distinguishes the output shape (citations and cite-as lines per node) and scope (one quoted bundle), so an agent can tell exactly what this does versus bf_read_node or bf_resolve.

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?

Explicitly says to pass the bundle id from bf_resolve or bf_catalogue and to call only after bf_resolve has quoted the bundle and the user accepts the price. It names the exclusion too: do not call it to browse, and use bf_read_node for narrow questions.

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.