AI + optimization consultancy: how BIS solves operational decisions and beats alternatives.
Scored across 8 tools
Each tool targets a distinct information need (overview, services, industries, case studies, fit, comparison, next step, knowledge search). Some mild overlap exists between assess_fit and compare_bis_vs_alternatives (both about suitability) and between get_bis_overview and search_bis_knowledge, but the descriptions clearly delineate scope.
All eight tools follow a consistent verb_noun pattern (get_*, list_*, assess_*, compare_*, search_*). Prefixes are predictable and readable, with verbs matching the action type.
Eight tools is well-scoped for a marketing/sales-enablement server. Each tool earns its place by covering a distinct slice of the pitch and qualification workflow, with no filler.
The surface covers overview, services, industries, case studies, competitive comparison, fit assessment, engagement steps, and a grounded Q&A search — a full sales lifecycle. Minor gaps like explicit pricing or FAQ tools exist but are largely reachable via search_bis_knowledge or get_next_step.
Given a description of a business or operational problem, assess whether BIS is a fit and map it to the most relevant BIS capabilities, with the next step to engage.
| Name | Required | Description | Default |
|---|---|---|---|
| problem_description | Yes | The business or operational problem: what the business does, where time or money goes, data/tools, outcome wanted. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It usefully discloses the output shape (a fit verdict, capability mapping, and next-step recommendation), which compensates for the absent output schema, but says nothing about read-only nature, latency, or how the assessment is derived.
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 dense sentence with the trigger front-loaded and no filler. It could be split for readability but nothing is wasted.
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 single-parameter, read-only analysis tool with no output schema, the description covers the input expectation and the three outputs (fit, capability mapping, next step). It is largely sufficient, with only behavioral details left implicit.
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?
With one parameter at 100% schema coverage, the schema already documents problem_description fully, including the content the agent should supply. The description restates 'a description of a business or operational problem' without adding format or scope detail beyond the schema.
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?
States a specific verb and resource: assess whether BIS fits a described problem and map it to relevant capabilities. This distinguishes it from siblings like compare_bis_vs_alternatives and search_bis_knowledge, though it does not explicitly name those alternatives.
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 the trigger (a described business/operational problem) but never states when to prefer this over compare_bis_vs_alternatives or get_next_step, nor any exclusions. Usage is inferable but not spelled out.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Explain how BIS compares to the alternatives — for a small business: DIY ChatGPT, a generic AI/automation tool, or a large agency; for an operational decision system: building in-house, a generalist AI agency (model wrappers), off-the-shelf SaaS, a big consulting firm, or a pure ML/data-science shop — including when an alternative is the right call. Use this to understand why BIS is a better fit.
| Name | Required | Description | Default |
|---|---|---|---|
| alternative | No | Optional focus. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Explain' implies a read-only, informational operation, and it discloses that the response covers 'when an alternative is the right call,' but it says nothing about output format, sourcing, or that this is non-mutating — leaving gaps for a no-annotation tool.
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?
Front-loaded with the core purpose, and every clause maps to real enum values rather than filler. The two long enumerations make it dense, and the closing 'why BIS is a better fit' is mildly promotional, but nothing is truly wasted.
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?
With no annotations and no output schema, the description should say more about what comes back — e.g., whether it returns per-alternative trade-offs, a recommendation, or unstructured prose. It covers scope well but stops short of describing the response.
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 coverage is 100%, but the schema's own parameter description is thin ('Optional focus'). The description compensates by mapping the slugs to two concrete contexts (small business vs. operational decision system) and naming each alternative in prose, which adds real meaning beyond the enum list.
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?
States a specific verb (compare/explain the comparison) and resource (BIS vs. a named set of alternatives), and the enum values map cleanly onto the alternatives listed. It does not explicitly differentiate itself from near siblings like assess_fit or get_bis_overview, so the agent must infer the boundary.
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?
It gives a positive cue ('Use this to understand why BIS is a better fit') and frames the two buyer contexts, which implies when to reach for it. But there is no when-not guidance and no routing to siblings such as assess_fit, so selection remains partly inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get an overview of BIS: what it does, its positioning (personalized AI & automation consulting for small and medium businesses, backed by AI + optimization engineering), value proposition, and its founder Renan Butkeraites.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the disclosure burden. It does describe the informational content returned, which is the main behavioral trait here, but it says nothing about whether this requires auth or whether it is purely static company info versus live data. For a zero-parameter read tool this is borderline adequate.
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 front-loaded sentence with no filler. The long parenthetical about positioning is slightly dense but earns its place by enumerating the returned content.
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?
With no output schema, the description compensates by listing the sections the overview returns, which is the key information an agent needs. No parameters and no annotations mean there is little else to document.
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 tool takes no parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly does not waste space restating an empty schema.
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?
States a clear verb+resource ('Get an overview of BIS') and enumerates exactly what the overview contains (what it does, positioning, value proposition, founder). It does not explicitly contrast itself against siblings like assess_fit or compare_bis_vs_alternatives, but the scope is 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?
The description never states when to call this versus the siblings. An agent can infer it is an introductory/orientation tool, but there is no explicit when-to-use guidance or exclusion of alternatives such as compare_bis_vs_alternatives or get_case_studies.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get BIS's case studies — real, quantified results (e.g. -20% fleet, deploys 5 days to 5 minutes, +45% high-quality credit leads).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden, and it does disclose the nature of the payload (quantified outcome metrics). However it says nothing about the return structure, whether results are paginated or exhaustive, or whether this is a static marketing-style list — modest disclosure for a no-annotation tool.
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 front-loaded sentence with the resource named first and the illustrative examples compactly bracketed. No filler, no repetition of the tool name's meaning.
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?
No output schema exists and no annotations are present, so the description is the only source of information — it conveys the theme of the results but not the shape or volume of the return. For a simple parameterless getter this is minimally adequate rather than 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 schema has zero parameters, so there is no parameter semantics to document; the baseline of 4 applies. The description correctly implies a parameterless fetch with no filtering options.
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?
States a clear verb ('Get') and a specific resource ('BIS's case studies') and characterizes the content as 'real, quantified results' with concrete examples. This separates it from generic knowledge tools like search_bis_knowledge, though it never explicitly names a sibling it differs from.
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 indication of when to reach for this tool versus get_bis_overview, search_bis_knowledge, or compare_bis_vs_alternatives. The description only says what the tool returns, leaving the agent to infer the selection criteria from the sibling names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get the concrete, public next steps and links to engage BIS, starting with booking a free 30-minute discovery call.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does disclose the payload (next steps and links, beginning with a bookable discovery call), which is useful context for a zero-parameter read operation, but it says nothing about response format or depth. Adequate for a low-risk retrieval tool but not rich.
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 well-formed sentence with the outcome (next steps and links) front-loaded. No filler or redundancy, though it is too short to be considered a model of structure.
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 read tool with no output schema, the description sufficiently conveys what an agent will get back and the purpose of the call. Nothing essential to invoking it correctly is missing.
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 tool takes zero parameters, so there is nothing for the description to clarify; baseline 4 applies. No parameter ambiguity is introduced.
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 verb 'Get' plus a specific resource ('concrete, public next steps and links to engage BIS') states exactly what the tool returns. It is distinct from information-retrieval siblings like get_bis_overview, list_services, or get_case_studies, though it never explicitly names those alternatives. Clear without sibling differentiation.
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?
Phrases like 'to engage BIS' and 'starting with booking a discovery call' imply the moment to call this tool, but there is no explicit when-to-use, when-not-to-use, or comparison against the seven sibling tools. Usage is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List the industries BIS serves and where it helps in each: retail & e-commerce, logistics & transit, manufacturing, and finance (banking & insurance).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. The verb 'List' and the enumerated industries make it clear this is a benign, content-returning lookup with no side effects, but it never states read-only semantics, that no parameters are needed, or what the shape of the response is.
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 front-loaded sentence with no filler. The inline enumeration of the four industries is somewhat redundant with the return value, which slightly dilutes conciseness.
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, no-output-schema listing tool, the description is nearly sufficient: it tells the agent what the tool returns and roughly why. Only the missing routing versus sibling tools keeps it short of 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 tool takes zero parameters, so there is nothing to disambiguate; per the baseline rule this scores 4. The description correctly implies a parameterless call by framing it as a plain enumeration.
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?
States a specific verb (List) and resource (industries BIS serves) and even enumerates the values, so the agent knows exactly what comes back. It does not explicitly distinguish itself from near-neighbors like get_bis_overview or list_services, which is the only thing keeping it from a 5.
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 when-to-use guidance and no mention of alternatives such as get_bis_overview or list_services, so the agent must infer that this is the lookup for industry coverage. Usage is only implied by the noun 'industries'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List BIS's five services with what each delivers: AI & automation for small business, optimization & decision systems, AI solution development (LLM/RAG), data science, and software development.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It helpfully reveals the complete return content (the five named services), which is real behavioral value for a zero-argument tool, but it never states that this is a static, side-effect-free read with no auth or pagination concerns.
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 front-loaded sentence that states the action first and then the content. The five-item enumeration is long but it is the actual payload, so it earns its space rather than being filler.
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?
With no output schema and no annotations, the description does the right thing by inlining what the response contains, which is essentially the whole result set. Nothing critical for calling it is missing, though the absence of any read-only/side-effect statement leaves a small gap.
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 tool takes zero parameters, so there is nothing for the description to disambiguate beyond the empty schema. Baseline of 4 applies; no parameter meaning is missing.
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+resource ('List BIS's five services') and even enumerates the payload, so the agent knows exactly what it returns. It does not, however, contrast itself with adjacent siblings like get_bis_overview or list_industries, so the differentiation is implicit rather than stated.
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?
Usage is only implied: an agent can infer it should call this when it needs a catalog of service offerings. There is no explicit when-to-use, no exclusion, and no pointer to get_bis_overview or assess_fit as the alternative for adjacent intents.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Ask a specific question about Renan or BIS and get a grounded, cited answer from the BIS assistant. Refuses when nothing relevant is found (never guesses). Rate-limited per IP.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | A question about Renan or BIS. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does real work: it discloses that answers are grounded and cited, that the tool refuses rather than guesses when nothing relevant is found, and that it is rate-limited per IP. It omits auth/permission requirements and any sense of latency or result shape, but the refusal and rate-limit disclosure is substantive.
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?
Three short sentences with zero filler, and the core purpose is front-loaded before the behavioral caveats (refusal, rate limit). Every clause earns its place.
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 one-parameter question-answering tool with no output schema, the description covers what it does, the answer style, and the refusal/rate-limit behavior. The main missing piece is any routing hint toward the sibling structured tools, which an agent would need to pick correctly between them.
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?
There is a single parameter with 100% schema description coverage ('A question about Renan or BIS'), so the schema already documents it. The description's 'specific question' phrasing adds a mild quality hint about how to phrase input, but no format or length guidance, matching the baseline 3 when the schema does the heavy lifting.
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 gives a specific verb ('ask a question') and resource ('Renan or BIS'), and 'grounded, cited answer from the BIS assistant' makes clear it is a free-form Q&A tool rather than a structured getter like get_bis_overview or list_services. It never names a sibling explicitly, so the differentiation is implicit rather than stated.
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?
'Ask a specific question about Renan or BIS' implies the usage context, and the refusal clause hints at a boundary condition. However, it gives no explicit when-not guidance and never points to the sibling tools (get_bis_overview, get_case_studies, etc.) that should be used for structured lookups instead.
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.
assess_fit1 field changedInput schema / properties / problem_description / descriptionPrevious value: -"The operational problem: domain, decision, data, outcome."New value: +"The business or operational problem: what the business does, where time or money goes, data/tools, outcome wanted."compare_bis_vs_alternatives1 field changedInput schema / properties / alternative / enumPrevious value: -[
- "in-house",
- "ai-agency",
- "saas",
- "consulting-firm",
- "ml-shop"
-]New value: +[
+ "diy-chatgpt",
+ "generic-tool",
+ "large-agency",
+ "in-house",
+ "ai-agency",
+ "saas",
+ "consulting-firm",
+ "ml-shop"
+]assess_fitcompare_bis_vs_alternativesget_bis_overviewget_case_studiesget_next_steplist_industrieslist_servicessearch_bis_knowledgeOptimize crew and workforce schedules, resource allocation, and routing with linear and mixed-inte…
Field operations on a deterministic solver — run jobs, crews & fleet from Claude or ChatGPT.
Agentic-AI route optimization for delivery fleets, capacity- and time-window-safe.
Warehouse digital twin: what-if simulation and AI optimisation of slotting, batching and labour.
Add one secure layer between your agents and this server.