Skip to main content
Glama
deenesjakoruzh
SkinnyMonk

EAG MCP Demo

by SkinnyMonk
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

EAG v3 — MCP demo with Prefab UI

A FastMCP server with three tools that exercise (1) the internet, (2) local-file CRUD, and (3) generative UI via Prefab. Designed to run inside Claude Desktop.

Tools

Tool

Type

Purpose

web_search(query)

internet

DuckDuckGo Instant Answer API — returns abstract + related topics

notes_file(action, key, content)

local CRUD

one tool, action-dispatched (create / read / update / delete / list) over ./notes.json

show_dashboard()

UI

renders saved notes as a Prefab card grid (uses @mcp.tool(app=True))

Related MCP server: MCP + CrewAI Agentic Integration

Setup

Requires uv (brew install uv) and Claude Desktop.

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

Wire into Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json and add (or merge) the mcpServers block:

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

Restart Claude Desktop. The MCP indicator should show eag-mcp-demo with three tools.

plain-Python fallback (no uv)

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

Then in Claude Desktop config use:

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

Demo prompt

Paste this in Claude Desktop after the server is wired up:

Find the ownership details of Tata Sons via web search, save a 2–3 sentence summary into my notes file under the key tata_sons, then open the dashboard so I can see it.

Expected behavior:

  1. web_search("Tata Sons ownership") → DDG abstract.

  2. notes_file("create", "tata_sons", "<summary>") → writes to notes.json.

  3. show_dashboard() → renders a Prefab card grid inline with one card.

Re-run with another company (e.g. "Reliance Industries") and the dashboard now shows two cards.

Smoke test

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

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

In the inspector: list tools, call web_search("Tata Sons"), then call notes_file("create", "x", "y") and confirm notes.json updates on disk.

Fallbacks

  • Prefab renderer doesn't engage (Claude Desktop returns JSON instead of UI): change the show_dashboard decorator from @mcp.tool(app=True) to plain @mcp.tool and have it return a Markdown table built from notes.json.

  • DuckDuckGo returns empty for the query: DDG only has Instant Answers for well-known entities. Use famous companies / people / places for the demo.

Files

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. Dates show when Glama detected each change.

  1. 3 tool updatesv0.1.0
    • First observednotes_file
    • First observedshow_dashboard
    • First observedweb_search
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.1/5.0
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
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

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
    297
    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.
    31
    Apache 2.0

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/SkinnyMonk/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server