Skip to main content
Glama

crystal_inspect

Read-onlyIdempotent

Read a CIF to list components with formal charges, atom counts, warnings, and per-model applicability. Use this read-only inspection to verify crystal data before energy workflows.

Instructions

Read a CIF: components with formal charges, atom count, warnings and per-model applicability. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cif_path": "<cif_path>"
    },
    "name": "crystal_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
cif_pathYesAbsolute path of the CIF file to inspect.

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
n_atomsNoAtoms in the unit cell.
warningsNo
componentsNo
applicability_by_modelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so 'Read-only' in the description is redundant rather than additive. The description does disclose what the read surfaces (charges, atom count, warnings, per-model applicability), which is mild added context, but since an output schema exists it does not break new behavioral ground.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence that front-loads the verb and resource before listing outputs. The trailing 'Read-only' is redundant with the annotations and is the only wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With rich annotations, a fully documented single parameter, and an output schema covering return values, the description covers what an agent needs to select and invoke the tool. It is slightly thin on when this is the right choice versus siblings, but nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter and schema description coverage is 100%, with the schema fully documenting cif_path as an absolute path. The description adds no syntax, format, or constraint detail beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Read') and resource ('a CIF'), and enumerates what the read yields: formal charges, atom count, warnings, per-model applicability. It is clearly distinguishable from status/help/plan/run/job siblings by operation type, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites (e.g., that the file must be a valid CIF on disk), and no mention of when another tool such as crystal_run or crystal_status would be preferred. The agent is left to infer intent from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.