Skip to main content
Glama
tenkai2018

ai-business-system-advisor-mcp

by tenkai2018

Recommend Next Step

recommend_next_step
Read-onlyIdempotent

Recommends a practical next step for your business workflow by analyzing goal, complexity, readiness, risk, and preferences to guide your AI or automation journey.

Instructions

Recommends a practical next-step category based on business goal, workflow complexity, implementation readiness, risk level, preferences, and missing information.

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.
timelineNoDesired timeline for review, documentation, pilot, or implementation.
userGoalNoGoal the user wants the next step to support.
readinessNoSimplified readiness level if already known.
riskLevelNoEstimated risk level or uncertainty for the workflow.
goal90DaysNoDesired business or workflow outcome over the next 90 days.
preferenceNoUser's preferred support style.
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.
wantsDoneForYouNoWhether the user prefers implementation support rather than self-guided work.
wantsSelfGuidedNoWhether the user prefers self-guided resources or templates.
problemComplexityNoEstimated complexity of the business or workflow problem.
hasExistingAutomationNoWhether the business already has automation or AI workflows in place.
implementationReadinessNoHow ready the business appears for implementation.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonYesReason this next-step category fits the supplied context.
confidenceYesConfidence level based on the clarity and completeness of the provided business context.
readinessLevelYesEstimated readiness level for the recommended path.
recommendedPathYesRecommended next-step category.
suggestedActionYesPractical action the user can take next.
alternativePathsYesOther reasonable next-step categories the user could consider.
missingInformationYesInformation the user should provide to improve routing confidence.
Behavior3/5

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

Annotations indicate readOnlyHint=true and idempotentHint=true, which are consistent with a recommendation tool. The description adds no behavioral context beyond what the annotations already provide. No destructive or side-effect details are needed, but the description does not elaborate on usage limits or failure modes.

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?

The description is a single sentence that is concise and front-loaded with the core purpose. No extraneous information is included, and it efficiently communicates the tool's function.

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

Completeness4/5

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

With an output schema present and 100% input schema coverage, the description is minimally adequate. However, for a complex tool with 23 parameters, a brief mention of the output's nature (e.g., 'category' or name) would enhance completeness, but is not strictly required given the structured fields.

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% with all 23 parameters described in the input schema. The tool description adds no additional meaning beyond these schema descriptions. Baseline score of 3 is appropriate when schema is fully self-documenting.

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 a specific verb 'Recommends' and resource 'next-step category', listing inputs like business goal and complexity. However, it does not differentiate from sibling tools such as 'recommend_first_workflow' or 'evaluate_ai_opportunities', which could overlap.

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

Usage Guidelines3/5

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

The description implies usage when the listed inputs are available but provides no explicit guidance on when to use this tool versus alternatives like 'recommend_first_workflow' or 'assess_trust_control_risks'. No when-not-to-use or exclusion criteria are given.

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