Local Intelligence 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_dataA | Analyze raw text using a local LLM. Provide the text and an instruction describing what analysis to perform (e.g., summarize, extract entities, format, find patterns in logs, etc.). The analysis runs entirely offline on your machine. |
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
With only one tool, there is no risk of confusion between tools. The single tool's purpose is clearly distinct by default.
A single tool trivially satisfies naming consistency. The name 'analyze_data' follows a clear verb_noun pattern.
A server named 'Local Intelligence Server' with only one tool feels under-scoped. Typically such servers offer multiple operations, making one tool too few for the apparent domain breadth.
The single tool covers the core purpose of text analysis via various instructions, but lacks specialized tools for common subtasks like data retrieval or different analysis modes, resulting in minor completeness gaps.