Skip to main content
Glama
deenesjakoruzh
Ronnie-Nutrition

EasyAiFlows Automation Assessment

by Ronnie-Nutrition
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

EasyAiFlows MCPサーバー

AIアシスタントがビジネスの自動化への準備状況を評価し、業界固有のAI自動化の推奨事項を提供するのを支援するMCP（Model Context Protocol）サーバーです。

ユーザーがClaude、ChatGPT、またはMCP互換のAIアシスタントに「どうすればビジネスを自動化できますか？」と尋ねると、このサーバーは実際の自動化の例と次のステップを含むパーソナライズされた診断を提供します。

ツール

assess_business_automation

業界や課題に基づいて、ビジネスのAI自動化への準備状況を診断します。

パラメータ:

パラメータ

必須

説明

industry

はい

ビジネスの業界（例: "dentists", "restaurants", "hvac"）

pain_points

いいえ

具体的な課題の配列（例: ["missed calls", "no-shows"]）

team_size

いいえ

チームの規模: "solo", "2-5", "6-15", "16-50", "50+"

current_tools

いいえ

現在使用しているツールの配列（例: ["Google Sheets", "Mailchimp"]）

戻り値: 自動化準備スコア（0-100）、業界固有の課題、時間短縮が見込める推奨自動化、および予約リンクを含む次のステップ。

get_automation_examples

特定の業界におけるAI自動化の実際の例を取得します。

パラメータ:

パラメータ

必須

説明

industry

はい

例を取得するビジネスの業界

戻り値: 説明、週あたりの短縮時間、全体的な影響統計、および完全な業界ガイドへのリンクを含む3つの実証済みの自動化例。

Related MCP server: essetech-ai-readiness-mcp

対応業界 (20)

歯科医、レストラン、HVAC（空調設備）、不動産、フィットネススタジオ、理髪店、ネイルサロン、メディカルスパ、カイロプラクター、保険代理店、住宅ローンブローカー、写真家、イベントプランナー、清掃サービス、造園業者、自動車修理、ペットグルーマー、保育園、教会、非営利団体

このサーバーはエイリアス（例: "gym" → fitness-studios, "mechanic" → auto-repair）も処理し、リストにない業界に対しても一般的な診断を提供します。

インストール

Claude Desktop

Claude Desktopの設定ファイル（Macの場合は ~/Library/Application Support/Claude/claude_desktop_config.json、Windowsの場合は %APPDATA%\Claude\claude_desktop_config.json）に追加してください：

{
  "mcpServers": {
    "easyaiflows": {
      "command": "node",
      "args": ["/path/to/easyaiflows-mcp-server/dist/server.js"]
    }
  }
}

Claude Code

claude mcp add easyaiflows node /path/to/easyaiflows-mcp-server/dist/server.js

ソースからビルド

git clone https://github.com/Ronnie-Nutrition/easyaiflows-mcp-server.git
cd easyaiflows-mcp-server
npm install
npm run build

使用例

インストール後、AIアシスタントに以下のように尋ねてください：

  • 「レストランの自動化準備状況を診断して。5人のチームで、電話の取りこぼしが多く、レビューへの返信ができていない。」

  • 「歯科医院向けのAI自動化にはどのようなものがありますか？」

  • 「清掃サービスを一人で運営していて、すべてGoogle Sheetsで管理しています。AIはどう役立ちますか？」

  • 「保険代理店向けの自動化の例を見せて。」

EasyAiFlowsについて

日々の業務から解放され、成長を目指す起業家のためのカスタムAI自動化。テキサス州ペアランドのRonnie Craigによって構築されました。

ライセンス

MIT

Available Tools

2 tools
assess_business_automationA

Assess a business's AI automation readiness based on their industry and pain points. Returns a personalized automation score, specific recommendations, and next steps.

ParametersJSON Schema
NameRequiredDescriptionDefault
industryYesThe business industry (e.g., 'dentists', 'restaurants', 'hvac', 'real-estate', 'fitness-studios', 'barbershops', 'nail-salons', 'med-spas', 'chiropractors', 'insurance-agents', 'mortgage-brokers', 'photographers', 'event-planners', 'cleaning-services', 'landscapers', 'auto-repair', 'pet-groomers', 'daycares', 'churches', 'nonprofits')
pain_pointsNoSpecific pain points the business is experiencing (e.g., 'missed calls', 'no-shows', 'slow lead response')
team_sizeNoNumber of people on the team
current_toolsNoTools currently being used (e.g., 'Google Sheets', 'QuickBooks', 'Mailchimp')

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It indicates the tool returns data (score, recommendations, next steps) but does not explicitly state whether it is read-only or if there are any side effects. This is adequate but could be more transparent.

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 concise with two sentences, front-loading the purpose and output. Every word adds value—no fluff, no redundancy. It efficiently communicates the tool's core 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?

Given the 4 parameters (with only one required), no output schema, and no annotations, the description adequately explains the tool's purpose and output. It could note that most parameters are optional, but the schema's 'required' field covers that. Overall, sufficient for an AI agent to understand usage.

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 baseline is 3. The description does not add any parameter-specific information beyond what is already in the schema; it only mentions 'industry and pain points' which are already documented. No additional semantic value is provided.

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's purpose: 'Assess a business's AI automation readiness' based on industry and pain points, and details the output: 'a personalized automation score, specific recommendations, and next steps.' This distinguishes it from the sibling tool 'get_automation_examples' which likely provides examples rather than an assessment.

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

Usage Guidelines4/5

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

The description implies when to use: when needing an automation readiness assessment. However, it does not explicitly contrast with the sibling tool 'get_automation_examples' or provide when-not-to-use scenarios. The context is clear but lacks explicit exclusions.

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

get_automation_examplesA

Get real examples of AI automations for a specific industry, including what they do, time saved, and revenue impact.

ParametersJSON Schema
NameRequiredDescriptionDefault
industryYesThe business industry to get examples for (e.g., 'dentists', 'restaurants', 'real-estate')

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided, so description must fully disclose behavior. It only mentions returned content types but omits details like read-only nature, authorization needs, rate limits, or response format.

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?

Single, front-loaded sentence that efficiently communicates purpose and output without superfluous words.

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?

For a simple tool with one parameter and no output schema, the description covers key output aspects but could include example count or response structure for greater completeness.

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 coverage is 100% with a clear parameter description; the tool description adds no additional meaning beyond what the schema already provides, achieving baseline.

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?

Description uses specific verb 'Get' and resource 'real examples of AI automations', clearly differentiating from sibling 'assess_business_automation' which assesses rather than retrieves examples.

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?

No explicit when-to-use or when-not-to-use guidance; context hints at usage for specific industries but does not differentiate from sibling tool or provide exclusion criteria.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv1.0.0
    • First observedassess_business_automation
    • First observedget_automation_examples
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one assesses automation readiness and provides recommendations, the other gives industry-specific examples. No overlap or ambiguity.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern (assess_* and get_*), making them predictable and easy to understand.

Tool Count3/5

With only 2 tools, the server feels thin for a comprehensive automation assessment service. While it covers core tasks, the count is borderline low for its apparent scope.

Completeness2/5

The tool surface is minimal, lacking capabilities to manage assessments over time, compare results, or handle follow-up actions. Significant gaps exist beyond one-shot queries.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • ai-visibility-mcp

    rccola990-cloud
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to check whether AI assistants recommend a brand and audit a site's AI-agent readiness, providing visibility scores and specific gaps.
    MIT

  • essetech-ai-readiness-mcp

    seppez89
    A
    license
    A
    quality
    D
    maintenance
    Enables AI assistants to assess a small business's AI readiness (0–100 score), suggest tailored AI use cases, describe Essetech's services, and book a free consultation.
    4
    7 npm
    MIT

  • geo-audit

    nycsav
    A
    license
    Not graded
    quality
    C
    maintenance
    Evaluates any website's AI visibility with 15 checks across crawlability, structure, content, and connectivity, and provides actionable fixes.
    1 npm
    MIT

  • hive-mcp-audit-readiness

    srotzin
    A
    license
    Not graded
    quality
    C
    maintenance
    Computes multi-jurisdictional AI compliance readiness scores with sourced penalty math, enabling gap analysis and audit tier recommendations.
    MIT