Skip to main content
Glama
tenkai2018

ai-business-system-advisor-mcp

by tenkai2018

Generate Mini Report

generate_mini_report
Read-onlyIdempotent

Generate a concise mini business system review including snapshot, bottlenecks, opportunities, risks, recommended workflow, and next step to assess AI opportunities and risks.

Instructions

Generates a public-safe mini business system review with snapshot, bottlenecks, opportunities, risks, first workflow, next step, 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.
risksNoKnown trust, control, customer, or implementation risks to include.
aiIdeaNoAI or automation idea the user is considering.
nextStepNoExisting next-step recommendation to include or refine.
teamSizeNoApproximate team size and key roles involved in the workflow.
confidenceNoOptional confidence level to carry into the report.
goal90DaysNoDesired business or workflow outcome over the next 90 days.
bottlenecksNoKnown bottlenecks to include in the mini review.
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.
opportunitiesNoKnown AI opportunities to include in the mini review.
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.
businessSnapshotNoExisting business snapshot to include or refine in the mini review.
preferredNextStepNoUser preference for self-guided, diagnostic, documentation, build, or review support.
recommendedWorkflowNoExisting first workflow recommendation to include or refine.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
confidenceYesConfidence level based on the clarity and completeness of the provided business context.
disclaimerYesPublic safety note explaining the limits of the review.
shortSummaryYesBrief summary of the review result.
reportMarkdownYesPublic-safe mini review formatted as markdown.
recommendedActionYesMost practical next action based on the supplied context.
missingInformationYesInformation the user should provide to improve report confidence.
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, establishing the tool as safe and non-destructive. The description adds the context 'public-safe', which aligns and reinforces this. No contradictions are present.

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 concisely lists the report's components. It is front-loaded with the core purpose. Given the tool's complexity (21 parameters), it is appropriately sized without being verbose.

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?

The description is adequate given the existence of an output schema and full parameter descriptions. However, it does not explain how the tool handles optional inputs or what happens when some information is missing, leaving some gaps for a complex tool.

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 description does not add additional meaning or relationships beyond listing the report components, so 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 it generates a 'mini business system review' and lists the specific components it includes. However, it does not explicitly differentiate from sibling tools like 'analyze_business_context' or 'map_customer_touchpoints', which could cause ambiguity.

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 for generating a mini review but does not provide guidance on when to use this tool over alternatives or when not to use it. Sibling tool names are listed but not referenced in the description to help the agent decide.

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