smugmug-docs-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_smugmug_docsA | Search the bundled SmugMug API documentation catalog. |
| fetch_smugmug_docA | Fetch content from a SmugMug docs page or a known docs path. |
| smugmug_api_callB | Call the live SmugMug API using pre-authorized OAuth credentials. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: searching the docs catalog, fetching a specific doc page, and making a live API call. No ambiguity between them.
The first two tools follow a verb_noun pattern (search_smugmug_docs, fetch_smugmug_doc), but the third (smugmug_api_call) flips to noun_verb. Also, singular 'doc' and plural 'docs' are inconsistent.
Three tools is on the lower end of the typical range, but it's well-scoped for a documentation-focused server. Each tool earns its place without unnecessary bloat.
The search and fetch tools cover the full documentation workflow—finding and retrieving content. The API call tool adds a complementary capability, leaving no obvious dead ends or missing core operations.