Skip to main content
Glama
DouglasGBailey

teaching-mcp-server

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
read_fileA

Read the full text contents of a file inside the server's sandboxed 'workspace' directory. Provide a path relative to the workspace root (e.g. 'welcome.txt' or 'notes/todo.txt').

write_fileA

Create or overwrite a text file inside the server's sandboxed 'workspace' directory. Parent directories are created automatically.

list_directoryA

List the files and subdirectories inside a directory within the server's sandboxed 'workspace'. Omit 'path' to list the workspace root.

add_noteA

Create a new persisted note with a title and body. Returns the generated note id, which is needed later to fetch or delete it.

list_notesA

List every stored note (id, title, and timestamps), most recently updated first. Use get_note to fetch a note's full body.

get_noteA

Fetch the full title and body of one note by its id.

delete_noteB

Permanently delete a note by its id.

fetch_urlA

Fetch the contents of a public http(s) URL and return the response body as text (truncated to a safe length). Useful for reading web pages, JSON APIs, or other public HTTP resources. Only http and https URLs are allowed.

get_system_infoA

Report information about the machine running this MCP server: operating system, CPU, memory, uptime, and current local time. Useful for diagnostics or environment-aware suggestions.

analyze_textA

Compute exact statistics for a block of text: character count, word count, line count, sentence count (approximate), and a SHA-256 hash. Useful whenever an exact count or checksum matters.

transform_textA

Deterministically transform text into a given case style: uppercase, lowercase, title_case, snake_case, or kebab_case.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 11 tools

Disambiguation5/5

Each tool targets a clearly distinct resource or operation: file sandbox operations, note CRUD, URL fetching, system info, and text analysis/transformation. The only potential overlap is between add_note/write_file and analyze_text/transform_text, but the descriptions sharply separate their purposes. An agent should have no trouble selecting the right tool.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: read_file, write_file, list_directory, add_note, list_notes, get_note, delete_note, fetch_url, get_system_info, analyze_text, transform_text. The convention is predictable throughout the set.

Tool Count5/5

With 11 tools, the server is well-scoped for a teaching/demo MCP server that showcases several capabilities. Each tool has a clear individual purpose and the count stays comfortably within a reasonable range without feeling bloated.

Completeness4/5

The surface covers file read/write/list, note create/list/get/delete, URL fetch, system info, and text analysis/transformation. Minor gaps exist: there is no file deletion/removal tool and no note update tool, though agents can work around these by overwriting files or deleting and recreating notes.

Maintenance

ActivityMaintained
ResponsivenessNo issues