Discover, route, and hand off enterprise operations problems without exposing private records.
Scored across 3 tools
Each tool occupies a distinct step: discover_capabilities lists capabilities, route_intent maps a specific problem to the best capability, and prepare_handoff produces a human handoff. Even though discover and route both relate to capabilities, their purposes are clearly separated by the descriptions.
All tools follow the same buildflow_ prefix with a consistent verb_noun pattern: discover_capabilities, prepare_handoff, route_intent. There is no style mixing or vague generic naming.
Three tools is well-scoped for a deliberately narrow capability-routing and handoff surface. Each tool has a clear, non-redundant role and earns its place.
For the stated scope of exposing capabilities, routing intents, and enabling safe human handoff, the surface is complete. It intentionally does not execute business actions, so the absence of execution/CRUD tools is a boundary rather than a gap.
Return BuildFlow's public currently wired enterprise-operations capabilities and safety boundaries.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions returning 'capabilities and safety boundaries' but does not state whether the call is read-only, has side effects, requires authentication, or what the response structure is. The disclosed scope is helpful but operational behavior remains opaque.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, direct sentence with no filler. It front-loads the action and clearly specifies what is returned, making it efficient for an agent to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter discovery tool, the description adequately captures what is returned. However, it could add context about when to invoke this relative to sibling tools or what an agent should do with the returned capabilities and safety boundaries. The lack of an output schema makes a bit more return-value context desirable, but overall the definition is reasonably complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters程 and schema description coverage is 100%, so there are no parameter details to elaborate. The baseline of 4 applies because no parameter information is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Return') and names a precise resource: BuildFlow's public currently wired enterprise-operations capabilities and safety boundaries. This clearly distinguishes it from the sibling tools (prepare_handoff, route_intent), which are about other phases of operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to call this tool versus the siblings, nor does it mention any prerequisites or sequencing (e.g., whether this should be called before routing or handoff). Usage context is entirely absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Prepare a privacy-preserving human handoff bundle. Does not transmit customer data or execute business actions.
| Name | Required | Description | Default |
|---|---|---|---|
| goal | No | ||
| problem | No | ||
| data_shape | No | ||
| constraints | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It does add a key safety trait: 'Does not transmit customer data or execute business actions,' which tells the agent it is a non-destructive, privacy-preserving operation. However, it does not describe what happens to the bundle, whether it is stored, or any permissions required. The single behavioral note is useful but incomplete.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise, using only two short sentences. It front-loads the core purpose and then adds a behavioral caveat. No wasted words, but it could be more informative without sacrificing brevity. The structure is efficient, though slightly sparse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 4 parameters and no output schema or annotations, the description is severely incomplete. It does not explain what a 'handoff bundle' is, what each parameter does, what the output format is, or any context for when it is appropriate. The agent would have to guess at parameter semantics and tool behavior. This is far below the minimum viable level.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 4 parameters (goal, problem, data_shape, constraints) with 0% description coverage, and the description provides no information about any of them. The agent has no guidance on what values to supply or their meaning. This is a critical gap that the description does not address at all.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear, specific action: 'Prepare a privacy-preserving human handoff bundle.' It also differentiates from siblings by noting it 'Does not transmit customer data or execute business actions,' which distinguishes it from buildflow_discover_capabilities and buildflow_route_intent. The verb 'prepare' and resource 'handoff bundle' are unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit guidance on when to use this tool versus the siblings. The description does not mention any conditions, prerequisites, or alternatives. While the purpose implies a handoff scenario, it does not state when an agent should choose this over buildflow_route_intent or buildflow_discover_capabilities.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Match an enterprise-operations problem to the smallest current BuildFlow capability. Never send private customer records.
| Name | Required | Description | Default |
|---|---|---|---|
| goal | No | ||
| intent | No | ||
| problem | No | ||
| data_shape | No | ||
| constraints | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It adds a meaningful safety constraint ('Never send private customer records'), which is useful context. However, it does not disclose other behavioral traits such as side effects, read-only status, or what happens after routing, leaving significant gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded, with the core purpose stated first and the safety directive second. Both sentences earn their place, though 'smallest current BuildFlow capability' is somewhat vague and could be clearer.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has five undocumented optional parameters, no output schema, no annotations, and two sibling tools, yet the description only provides a one-line purpose and a safety warning. It does not explain how to use the parameters, what the tool returns, or how it relates to discover_capabilities and prepare_handoff, making it incomplete for reliable invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description provides no explanation of the five parameters (goal, intent, problem, data_shape, constraints). The phrase 'enterprise-operations problem' only loosely maps to the schema and does not clarify the role of each parameter. The description fails to compensate for the complete lack of schema-level documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action ('Match an enterprise-operations problem to the smallest current BuildFlow capability'), which clearly identifies the tool's core purpose. It does not explicitly name sibling tools, but the focus on routing to a capability distinguishes it from discover_capabilities and prepare_handoff at a basic level.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use when an enterprise-operations problem needs to be matched to a BuildFlow capability, but it provides no explicit when-to-use or when-not-to-use guidance. It also does not mention alternatives or explain how this tool differs from its siblings, leaving the agent to infer selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
buildflow_discover_capabilitiesbuildflow_prepare_handoffbuildflow_route_intentSearch PII-free opportunities, availability, and live events; prepare safe no-write form handoffs.
Reliability intelligence: production incidents, risk register, controls catalog, knowledge graph.
Match contractor operating problems to practical Field Library playbooks. Read-only discovery.
Securely query and analyze business data, dashboards, projections, alerts, and knowledge.
Add one secure layer between your agents and this server.