EAG MCP Demo

by SkinnyMonk

Overview Schema Source Related Servers Discussions Admin

Python

Local

show_dashboard

Display saved notes in a card grid for visual review after saving. Refreshes by reading notes.json on each call.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "show_dashboard"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Implementation Reference

server.py:127-162 (handler)

The core handler function for the 'show_dashboard' tool. Loads notes from notes.json, builds a PrefabApp UI with a heading, summary text, and a card grid (or empty state). Returns the PrefabApp instance for rendering.

def show_dashboard() -> PrefabApp:
    """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.
    """
    notes = _load_notes()
    items = [{"key": k, "body": v[:400]} for k, v in sorted(notes.items())]

    if NOTES.exists():
        ts = datetime.datetime.fromtimestamp(NOTES.stat().st_mtime)
        last_updated = ts.strftime("%Y-%m-%d %H:%M")
    else:
        last_updated = "never"

    state = {
        "notes": items,
        "count": len(items),
        "last_updated": last_updated,
    }

    with PrefabApp(state=state, css_class="p-6") as app:
        Heading("My Notes")
        Text("{{ count }} note(s) - last updated {{ last_updated }}")
        if items:
            with Grid(columns={"default": 1, "md": 2}, gap=4):
                with ForEach("notes"):
                    with Card():
                        with CardContent():
                            Heading("{{ key }}")
                            Text("{{ body }}")
        else:
            with Card():
                with CardContent():
                    Text("No notes yet - call notes_file('create', ...) first.")
    return app

server.py:126-127 (registration)
Registers 'show_dashboard' as an MCP tool using the @mcp.tool(app=True) decorator, indicating it returns a PrefabApp (not a plain string).
```
@mcp.tool(app=True)
def show_dashboard() -> PrefabApp:
```

server.py:19-23 (helper)

Helper function _load_notes() used by show_dashboard to read notes from the local notes.json file.

def _load_notes() -> dict[str, str]:
    if not NOTES.exists():
        return {}
    raw = NOTES.read_text().strip()
    return json.loads(raw) if raw else {}

server.py:127-127 (schema)
The tool takes no parameters (empty schema) and returns a PrefabApp. The docstring describes its purpose and when to call it.
```
def show_dashboard() -> PrefabApp:
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 16, 2026

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.

Deploy Server