materials-studio-mcp-moc

ms_castep_gateway_readiness

Inspect the local Gateway to detect and report CASTEP submission blockers, enabling resolution before job submission.

Instructions

Inspect the local Gateway and report CASTEP submission blockers without submitting.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ms_castep_gateway_readiness"
  }
}

Input Schema

Name	Required	Description	Default
`requested_cores`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description must carry the behavioral burden. It states 'inspect' and 'without submitting', which strongly implies read-only, non-destructive behavior. However, it omits details about what it actually checks (e.g., executables, licenses, resources) and does not explicitly state that it makes no changes, leaving some ambiguity.

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

Conciseness5/5

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

The description is a single, front-loaded sentence that contains no extraneous words. Every element—inspection, local scope, CASTEP blockers, and non-submission—adds necessary value.

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

Completeness3/5

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

This is a simple tool with one optional parameter and an output schema, so the description doesn't need to explain return values. The core purpose and non-submission safety are clear, but the missing parameter semantics and lack of context about the Gateway setup leave the description only partially complete for correct invocation.

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

Parameters2/5

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

The schema description coverage is 0%, and the description does not mention 'requested_cores' at all. It fails to explain how the parameter influences the readiness check or what the default of 12 means. The agent is left to infer from the parameter name alone, which is insufficient.

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

Purpose5/5

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

The description clearly identifies the action (inspect and report), the resource (local Gateway), the subject (CASTEP submission blockers), and a critical constraint (without submitting). This specificity distinguishes it from sibling tools that check status, health, or submission execution.

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

Usage Guidelines4/5

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

The phrase 'without submitting' clearly establishes the tool as a pre-submission readiness check, implying usage before an actual CASTEP job submission. It provides clear context for when to use, but it does not explicitly name alternative tools or exclusion scenarios, so full differentiation from siblings is missing.

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

Deploy Server