Skip to main content
Glama
deenesjakoruzh
SkinnyMonk

EAG MCP Demo

by SkinnyMonk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

EAG v3 — Prefab UI を備えた MCP デモ

(1) インターネット、(2) ローカルファイルのCRUD、(3) Prefab を介した生成UI、という3つのツールを備えた FastMCP サーバーです。Claude Desktop 内で実行するように設計されています。

ツール

ツール

タイプ

目的

web_search(query)

インターネット

DuckDuckGo Instant Answer API — 概要と関連トピックを返します

notes_file(action, key, content)

ローカル CRUD

1つのツールで、./notes.json に対してアクション（create / read / update / delete / list）をディスパッチします

show_dashboard()

UI

保存されたノートを Prefab カードグリッドとしてレンダリングします（@mcp.tool(app=True) を使用）

Related MCP server: MCP + CrewAI Agentic Integration

セットアップ

uv (brew install uv) と Claude Desktop が必要です。

cd /Users/nitingangwar/Documents/Code/eagv3/mcp
uv sync

Claude Desktop への接続

~/Library/Application Support/Claude/claude_desktop_config.json を編集し、mcpServers ブロックを追加（またはマージ）します：

{
  "mcpServers": {
    "eag-mcp-demo": {
      "command": "/opt/homebrew/bin/uv",
      "args": [
        "run",
        "--directory",
        "/Users/nitingangwar/Documents/Code/eagv3/mcp",
        "python",
        "server.py"
      ]
    }
  }
}

Claude Desktop を再起動します。MCP インジケーターに eag-mcp-demo と3つのツールが表示されるはずです。

Python 単体でのフォールバック（uv なし）

python3 -m venv .venv
.venv/bin/pip install -e .

その後、Claude Desktop の設定で以下を使用します：

"command": "/Users/nitingangwar/Documents/Code/eagv3/mcp/.venv/bin/python",
"args": ["/Users/nitingangwar/Documents/Code/eagv3/mcp/server.py"]

デモ用プロンプト

サーバーを接続した後、Claude Desktop に以下を貼り付けてください：

Web検索で Tata Sons の所有権の詳細を調べ、2〜3文の要約を tata_sons というキーでノートファイルに保存し、ダッシュボードを開いて確認できるようにしてください。

期待される動作：

  1. web_search("Tata Sons ownership") → DDG の概要を取得。

  2. notes_file("create", "tata_sons", "<summary>") → notes.json に書き込み。

  3. show_dashboard() → 1枚のカードを含む Prefab カードグリッドをインラインでレンダリング。

別の企業（例：「Reliance Industries」）で再実行すると、ダッシュボードに2枚のカードが表示されます。

スモークテスト

# Server starts and blocks on stdin (correct):
uv run python server.py

# Or interactive inspector:
npx @modelcontextprotocol/inspector uv run python server.py

インスペクターで、ツールをリストアップし、web_search("Tata Sons") を呼び出し、次に notes_file("create", "x", "y") を呼び出して、ディスク上の notes.json が更新されることを確認します。

フォールバック

  • Prefab レンダラーが動作しない場合（Claude Desktop が UI ではなく JSON を返す）：show_dashboard デコレーターを @mcp.tool(app=True) から通常の @mcp.tool に変更し、notes.json から構築された Markdown テーブルを返すようにします。

  • DuckDuckGo がクエリに対して空の結果を返す場合：DDG は有名なエンティティに対してのみ Instant Answer を持っています。デモには有名な企業、人物、場所を使用してください。

ファイル

server.py        # FastMCP server with the 3 tools
notes.json       # backing store for notes_file (starts as {})
pyproject.toml   # deps: fastmcp[apps], prefab-ui==0.19.1, httpx

Available Tools

3 tools
notes_fileA

CRUD on local notes.json.

Actions:

  1. create - add a new note: action='create', key='foo', content='...'

  2. read - fetch one note: action='read', key='foo'

  3. update - replace existing: action='update', key='foo', content='...'

  4. delete - remove a note: action='delete', key='foo'

  5. list - list all keys: action='list'

ParametersJSON Schema
NameRequiredDescriptionDefault
actionYes
keyNo
contentNo

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It lists actions but does not mention potential destructive effects (update/delete), error handling, atomicity, or file locking. The transparency is minimal beyond basic CRUD semantics.

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 a single introductory line followed by a list of actions and examples. Every sentence serves a purpose, and the structure is front-loaded with the core purpose.

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 tool's simplicity (3 parameters, output schema present), the description covers the action parameter well. However, it does not clarify behavior for empty 'key' or 'content' defaults, nor potential side effects. Still, it is largely complete for a basic CRUD tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, but the description adds meaningful context by providing examples for each action, clarifying how 'key' and 'content' are used per action. This adds value beyond the schema definition.

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 'CRUD on local notes.json' and enumerates each action with examples, making the tool's purpose unmistakable. It is distinct from siblings 'show_dashboard' and 'web_search'.

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 implicitly conveys when to use the tool (to manage notes), but does not provide explicit guidance on when not to use it or discuss alternatives. Given the unrelated siblings, no confusion arises, but explicit exclusions are absent.

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

show_dashboardA

Render saved notes as a Prefab card grid.

Call this AFTER saving notes via notes_file to display them visually to the user. Reads notes.json fresh on each call.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.6/5.0
Behavior4/5

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

Despite no annotations, the description discloses that it reads notes.json fresh on each call, informing the agent about data source and potential performance. Missing edge cases like missing notes.json, but sufficient for a simple tool.

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?

Two sentences with no redundancy. Front-loaded purpose, then usage and behavior. Every sentence adds value.

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 zero-param, no-output-schema tool, the description covers main action, usage context, and a behavioral trait. Misses what happens when no notes exist, but overall adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so schema coverage is 100%. The description provides no extra param info, but baseline for zero-param tools is 4.

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 renders saved notes as a Prefab card grid. It uses a specific verb-resource combination and distinguishes itself from siblings (notes_file for saving, web_search unrelated).

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

Usage Guidelines5/5

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

Explicitly instructs to call AFTER saving via notes_file, establishing a clear ordering and naming the prerequisite sibling. This guides the agent on when to invoke the tool.

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. 3 tool updatesv0.1.0
    • First observednotes_file
    • First observedshow_dashboard
    • First observedweb_search
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation5/5

The three tools cover completely different areas: local note CRUD (notes_file), visual dashboard (show_dashboard), and external web search (web_search). There is no overlap or ambiguity.

Naming Consistency4/5

All tool names use snake_case and are descriptive, though the pattern varies slightly (notes_file is a noun, show_dashboard is verb+noun, web_search is noun+verb). Still consistent and readable.

Tool Count4/5

With only 3 tools, the set is small but well-suited for a demo server. Each tool has a clear purpose and none feel redundant. A few more tools might be expected for a full-featured service, but for a demo it's appropriate.

Completeness5/5

The notes_file tool provides full CRUD and listing, show_dashboard adds visualization, and web_search covers external search. There are no obvious gaps for the stated demo purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Custom Context MCP Server

    jiliangmason
    A
    license
    Not graded
    quality
    D
    maintenance
    A FastMCP-based server that supports SSE real-time event streaming and tool calling, with features for text-to-JSON conversion and grouping text by JSON templates.
    MIT

  • Forgetful

    ScottRBK
    A
    license
    A
    quality
    A
    maintenance
    A storage and retrieval MCP server for AI agents using FastMCP, enabling persistent knowledge base with semantic search and automatic linking.
    3
    231 PyPI
    339
    MIT

  • mnemos

    ncz-os
    A
    license
    Not graded
    quality
    B
    maintenance
    MCP server providing persistent memory, semantic search, versioned storage, webhook fanout, and unified LLM routing for AI agents via FastAPI runtime with multiple backend options.
    35
    Apache 2.0