codex-local-ollama-mcp
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| local_textB | Create a labeled local draft from self-contained user-provided text only; never use for facts, high-stakes or operational work. |
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 1 tool
Only one tool exists, so there is no possibility of confusing it with others. The tool's purpose is clearly limited to creating a labeled local draft from user text.
With a single tool, there are no naming inconsistencies to flag. However, the name 'local_text' does not follow a clear verb_noun pattern, making it impossible to infer a broader convention.
A single tool is far too few for a server with a broad name like 'codex-local-ollama-mcp'. The tool itself appears limited and trivial relative to the implied scope, creating an extreme mismatch.
The server offers only one narrow operation, with no apparent CRUD lifecycle, retrieval, or management capabilities. The domain hinted by the server name is severely underrepresented, leaving agents without essential functionality.