Skip to main content
Glama
SkinnyMonk

EAG MCP Demo

by SkinnyMonk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
web_searchA

Search the web via DuckDuckGo Instant Answer API.

Returns a plain-text block with the abstract, source URL, and top related topics. Best for well-known entities (companies, people, places). Returns 'no results' if the query has no instant answer.

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'

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Prefab Renderer (show_dashboard)
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

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