Skip to main content
Glama
tenkai2018

ai-business-system-advisor-mcp

by tenkai2018

Analyze Business Context

analyze_business_context
Read-onlyIdempotent

Summarizes business context including customer, offer, workflow, goals, and constraints to identify missing information, readiness signals, and confidence for AI workflow review.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoAny additional context the user wants considered in the review.
offerNoCore product, service, package, or outcome the business sells.
aiIdeaNoAI or automation idea the user is considering.
teamSizeNoApproximate team size and key roles involved in the workflow.
goal90DaysNoDesired business or workflow outcome over the next 90 days.
constraintsNoKnown constraints such as budget, team capacity, tools, timeline, compliance needs, or data access.
currentGoalNoCurrent business goal the user wants the review to support.
businessTypeNoType of business, such as ecommerce, SaaS, consulting, agency, local service, or solo business.
revenueModelNoHow the business earns revenue, such as projects, retainers, subscriptions, services, or products.
riskConcernsNoConcerns related to customer trust, brand reputation, legal exposure, sensitive data, or quality control.
currentProblemNoMain business or workflow problem the user wants to solve.
targetCustomerNoPrimary customer segment or buyer the business serves.
currentWorkflowNoHow the relevant workflow currently works, including manual steps, tools, handoffs, and review points.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
confidenceYesConfidence level based on the clarity and completeness of the provided business context.
businessSnapshotYesConcise public-safe summary of the business and operating context.
readinessSignalsYesSignals that indicate whether the business is ready for AI-assisted workflow design.
missingInformationYesInformation the user should provide to improve diagnostic confidence.
likelyBusinessModelYesLikely business model inferred from the supplied context.
targetCustomerSummaryYesShort summary of the customer segment or buyer context.
valuePromiseHypothesisYesHypothesis about the core value promise or outcome the business sells.
primaryConstraintHypothesisYesLikely main constraint limiting progress or readiness.
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds no behavioral context beyond listing output elements like confidence and missing information.

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?

Single sentence, no fluff. However, the list of included items is somewhat generic and could be more structured.

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?

With many optional parameters and an output schema, the description is adequate but vague. It does not explain how missing information or confidence is handled.

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?

All 13 parameters have schema descriptions (100% coverage), so the tool description adds no additional meaning. Baseline 3 is appropriate.

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 clearly states the tool summarizes business context and lists specific elements (customer, offer, workflow, etc.), distinguishing it from sibling tools that focus on specific aspects like bottlenecks or touchpoints.

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?

No guidance on when to use this tool versus alternatives like map_customer_touchpoints or evaluate_ai_opportunities. The description does not specify prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tenkai2018/ai-business-system-advisor-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server