crystal-energy-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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| crystal_statusB | Version, device and available models with their element coverage, charge support and weight licence. Read-only; call first. |
| crystal_helpB | Short guidance for one topic (overview, validate, lattice_energy, pairs, series, workflow, errors); topic workflow attaches the workflow JSON Schema. |
| crystal_inspectB | Read a CIF: components with formal charges, atom count, warnings and per-model applicability. Read-only. |
| crystal_planB | Build and resolve a workflow for one task over one or more CIFs, write it to disk (idempotent) and estimate its size. Every default becomes explicit. |
| crystal_runA | Start a resolved workflow as a job. Reusing an idempotency_key returns the same job_id instead of starting another job. |
| crystal_jobB | Job state, new events after after_event_seq, up to 50 summary rows, result file paths and the provenance file. Read-only. |
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 6 tools
Each tool has a distinct role: status for environment, help for guidance, inspect for CIF parsing, plan for workflow construction, run for job submission, and job for monitoring. The read-only annotations and task-specific verbs make misselection unlikely.
All tools use the same `crystal_` prefix and lower snake_case suffix, with no casing or delimiter inconsistencies. Although suffixes mix nouns and verbs, the convention is uniform and predictable.
Six tools is well-scoped for a workflow-oriented MCP server. Each tool covers a necessary stage without redundancy or bloat.
The surface covers the core lifecycle: environment check, help, CIF inspection, workflow planning, job submission, and job monitoring/results. It lacks explicit job cancellation/listing and a standalone validation tool, but these are minor gaps for the main workflow.