Skip to main content
Glama
tenkai2018

ai-business-system-advisor-mcp

by tenkai2018

Export Intake Packet

export_intake_packet
Read-onlyIdempotent

Creates a structured intake packet combining business context, findings, risks, and workflow recommendations into a shareable markdown and JSON document.

Instructions

Creates a structured public-safe markdown and JSON intake packet with business context, findings, risks, recommended workflow, 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.
userNotesNoAdditional notes the user wants included in the intake packet.
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.
riskSummaryNoStructured trust and control risk findings from a prior tool result.
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.
touchpointMapNoStructured customer touchpoint map from a prior tool result.
currentProblemNoMain business or workflow problem the user wants to solve.
targetCustomerNoPrimary customer segment or buyer the business serves.
businessContextNoStructured business context from a prior tool result or user notes.
currentWorkflowNoHow the relevant workflow currently works, including manual steps, tools, handoffs, and review points.
bottleneckSummaryNoStructured bottleneck findings from a prior tool result.
preferredNextStepNoPreferred next-step category or support style to include in the packet.
opportunitySummaryNoStructured AI opportunity findings from a prior tool result.
recommendedNextStepNoStructured next-step recommendation from a prior tool result.
recommendedWorkflowNoStructured first workflow recommendation from a prior tool result.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
confidenceYesConfidence level based on the clarity and completeness of the provided business context.
packetJsonYesStructured intake packet data for handoff or deeper review.
packetMarkdownYesPublic-safe intake packet formatted as markdown.
missingInformationYesInformation the user should provide before deeper review or implementation.
recommendedPrivateReviewYesPublic-safe recommendation for the next deeper review category.
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds 'public-safe' but doesn't disclose any additional behavioral traits beyond the output format.

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 front-loads the core action and output. It's concise but could be more structured (e.g., paragraph with bullets).

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 complexity (22 parameters, many optional, nested objects, output schema exists), the description is minimal. It doesn't explain the relationship to sibling tools or that this aggregates prior results. The output schema may compensate, but the description lacks sufficient context.

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 all 22 parameters. The description adds no extra meaning or context about parameters beyond what is in the schema.

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 action (creates) and the output (structured markdown and JSON intake packet with specific contents). It implies this is a final export tool, but doesn't explicitly differentiate from sibling analysis tools.

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 explicit guidance on when to use this tool versus alternatives. It's implied as a final step after other analysis tools, but no when-not or prerequisites are mentioned.

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