Agent Context Token Optimizer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOKEN_OPTIMIZER_OWNER | Yes | Opaque identifier for the MCP process owner, generated and bound by the host. Must not be chosen by the model. |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| store_tool_resultB | Explicitly store non-sensitive text in this process owner's local vault. Supplied text may already count toward host context. |
| read_omitted_contentC | Read one bounded page from this process owner's local vault. |
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 2 tools
The two tools have clearly distinct purposes: one stores text, the other reads a stored page. No overlap.
Both tool names follow a consistent verb_noun pattern: store_tool_result and read_omitted_content.
With only 2 tools, the server feels minimal but could be acceptable for a narrowly focused functionality. It is borderline.
Missing essential operations like deleting, updating, or listing stored content, which are needed for full lifecycle management.