Lithic 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_resourceC | Get a specific Lithic resource by ID |
| list_resourcesC | List resources of a specific type |
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: get_resource retrieves a single resource by ID, while list_resources retrieves multiple resources of a type. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern (get_resource and list_resources), using snake_case and clear action verbs. The naming is perfectly predictable and uniform.
With only 2 tools, the server feels too thin for a general-purpose resource management domain. It lacks essential operations like create, update, or delete, making it incomplete for typical CRUD workflows.
The tool surface is severely incomplete for resource management. It only supports read operations (get and list), missing create, update, and delete capabilities, which are fundamental for a full lifecycle.