mcp-oeis
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 | {
"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
| Name | Description |
|---|---|
| get_sequence_by_idA | Get a sequence by its OEIS ID (e.g., "A000109" for simplicial polyhedra, "A000045" for Fibonacci). |
| search_by_termsA | Search OEIS sequences by providing integer terms. For example, searching [1,1,2,3,5,8] will find the Fibonacci sequence. |
| search_by_nameB | Search OEIS sequences by name or keyword. For example, searching "Fibonacci" will find Fibonacci-related sequences. |
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 distinct purpose: fetching by ID, searching by name, and searching by integer terms. No overlap or confusion possible.
All tool names follow a consistent verb_noun pattern with snake_case (get_sequence_by_id, search_by_name, search_by_terms).
Three tools cover the essential operations for an OEIS server: direct retrieval by ID and two search methods (by name and by terms). This is well-scoped without unnecessary bloat.
The tool surface covers the primary use cases (fetching a specific sequence and searching). A minor gap is the lack of batch retrieval or filtering by other metadata (e.g., author), but the core functionality is present.