Personal Context Technology 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 | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| updateContextD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Complete Context | |
| All Sections | |
| basic_info | |
| preferences | |
| instruction | |
| metadata |
TDQS
Scored across 1 tool
Only one tool exists, so there is no ambiguity among tools. However, the lack of description means it's impossible to understand its purpose, making selection meaningless.
The single tool uses camelCase. With only one tool, consistency cannot be evaluated meaningfully, so a neutral score is given.
A single tool with no description is far too few for a meaningful server. It suggests minimal utility and incomplete implementation.
With only one tool and no description, the tool surface is severely incomplete. The server's purpose is unknown, and no workflows can be supported.