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를 활용하는 세 가지 도구가 포함된 FastMCP 서버입니다. Claude Desktop 내에서 실행되도록 설계되었습니다.

도구

도구

유형

목적

web_search(query)

인터넷

DuckDuckGo Instant Answer API — 요약 및 관련 주제 반환

notes_file(action, key, content)

로컬 CRUD

단일 도구, ./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가 나타나야 합니다.

일반 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에 다음을 붙여넣으세요:

웹 검색을 통해 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() → 하나의 카드가 포함된 Prefab 카드 그리드를 인라인으로 렌더링.

다른 회사(예: "Reliance Industries")로 다시 실행하면 대시보드에 두 개의 카드가 표시됩니다.

스모크 테스트

# 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'

NameRequiredDescriptionDefault
actionYes
keyNo
contentNo

Output 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.

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
    120 PyPI
    340
    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