AI Business System Advisor

by io.github.tenkai2018

Analyze Business Context

analyze_business_context

Read-onlyIdempotent

Summarizes the supplied business context, including customer, offer, workflow, goals, constraints, readiness signals, missing information, and confidence.

Input Schema

TableJSON Schema

Name	Required	Description
`notes`	No	Any additional context the user wants considered in the review.
`offer`	No	Core product, service, package, or outcome the business sells.
`aiIdea`	No	AI or automation idea the user is considering.
`teamSize`	No	Approximate team size and key roles involved in the workflow.
`goal90Days`	No	Desired business or workflow outcome over the next 90 days.
`constraints`	No	Known constraints such as budget, team capacity, tools, timeline, compliance needs, or data access.
`currentGoal`	No	Current business goal the user wants the review to support.
`businessType`	No	Type of business, such as ecommerce, SaaS, consulting, agency, local service, or solo business.
`revenueModel`	No	How the business earns revenue, such as projects, retainers, subscriptions, services, or products.
`riskConcerns`	No	Concerns related to customer trust, brand reputation, legal exposure, sensitive data, or quality control.
`currentProblem`	No	Main business or workflow problem the user wants to solve.
`targetCustomer`	No	Primary customer segment or buyer the business serves.
`currentWorkflow`	No	How the relevant workflow currently works, including manual steps, tools, handoffs, and review points.

Output Schema

TableJSON Schema

Name	Required	Description
`confidence`	Yes	Confidence level based on the clarity and completeness of the provided business context.
`businessSnapshot`	Yes	Concise public-safe summary of the business and operating context.
`readinessSignals`	Yes	Signals that indicate whether the business is ready for AI-assisted workflow design.
`missingInformation`	Yes	Information the user should provide to improve diagnostic confidence.
`likelyBusinessModel`	Yes	Likely business model inferred from the supplied context.
`targetCustomerSummary`	Yes	Short summary of the customer segment or buyer context.
`valuePromiseHypothesis`	Yes	Hypothesis about the core value promise or outcome the business sells.
`primaryConstraintHypothesis`	Yes	Likely main constraint limiting progress or readiness.

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedJul 27, 2026

addedInput schema / properties / aiIdea / description

Added value: +"AI or automation idea the user is considering."

addedInput schema / properties / businessType / description

Added value: +"Type of business, such as ecommerce, SaaS, consulting, agency, local service, or solo business."

addedInput schema / properties / constraints / description

Added value: +"Known constraints such as budget, team capacity, tools, timeline, compliance needs, or data access."

addedInput schema / properties / currentGoal / description

Added value: +"Current business goal the user wants the review to support."

addedInput schema / properties / currentProblem / description

Added value: +"Main business or workflow problem the user wants to solve."

addedInput schema / properties / currentWorkflow / description

Added value: +"How the relevant workflow currently works, including manual steps, tools, handoffs, and review points."

addedInput schema / properties / goal90Days / description

Added value: +"Desired business or workflow outcome over the next 90 days."

addedInput schema / properties / notes / description

Added value: +"Any additional context the user wants considered in the review."

addedInput schema / properties / offer / description

Added value: +"Core product, service, package, or outcome the business sells."

addedInput schema / properties / revenueModel / description

Added value: +"How the business earns revenue, such as projects, retainers, subscriptions, services, or products."

addedInput schema / properties / riskConcerns / description

Added value: +"Concerns related to customer trust, brand reputation, legal exposure, sensitive data, or quality control."

addedInput schema / properties / targetCustomer / description

Added value: +"Primary customer segment or buyer the business serves."

addedInput schema / properties / teamSize / description

Added value: +"Approximate team size and key roles involved in the workflow."

addedOutput schema / properties / businessSnapshot / description

Added value: +"Concise public-safe summary of the business and operating context."

addedOutput schema / properties / confidence / description

Added value: +"Confidence level based on the clarity and completeness of the provided business context."

addedOutput schema / properties / likelyBusinessModel / description

Added value: +"Likely business model inferred from the supplied context."

addedOutput schema / properties / missingInformation / description

Added value: +"Information the user should provide to improve diagnostic confidence."

addedOutput schema / properties / primaryConstraintHypothesis / description
```
Added value: +"Likely main constraint limiting progress or readiness."
```

addedOutput schema / properties / readinessSignals / description

Added value: +"Signals that indicate whether the business is ready for AI-assisted workflow design."

addedOutput schema / properties / targetCustomerSummary / description

Added value: +"Short summary of the customer segment or buyer context."

addedOutput schema / properties / valuePromiseHypothesis / description

Added value: +"Hypothesis about the core value promise or outcome the business sells."

First observedMay 30, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's 'summarizes' aligns. The description adds that it includes 'readiness signals, missing information, and confidence', but does not elaborate on behavior like whether it generates AI-based analysis or caching. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that effectively front-loads the tool's purpose. It is relatively concise, though listing many categories makes it a bit dense. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 13 parameters and an output schema (not shown but present), the description provides enough context for basic understanding. However, it lacks details on how the summary is generated or what 'confidence' means. An output schema exists, so return values need not be described. Overall adequate but not fully comprehensive.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents each parameter. The tool description only lists categories (e.g., 'customer, offer, workflow') without adding new meaning to individual parameters. Thus, it meets the baseline but does not exceed it.

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?

The description clearly states the verb 'summarizes' and identifies the resource as 'supplied business context'. It lists the categories included, making the purpose evident. However, it does not explicitly differentiate from sibling tools, which focus on specific aspects like risks or opportunities.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'assess_trust_control_risks' or 'evaluate_ai_opportunities'. There is no mention of prerequisites, excluded scenarios, or decision context.

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

All AI Business System Advisor tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.