materials-studio-mcp-moc

md_prepare_production_confirmation

Generate a short-lived, single-use confirmation token to authorize an exact production operation, ensuring secure and auditable execution of Materials Studio workflows.

Instructions

Issue a short-lived, single-use confirmation for an exact production operation.

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": {
      "tool_name": "<tool_name>",
      "parameters": "<parameters>"
    },
    "name": "md_prepare_production_confirmation"
  }
}

Input Schema

Name	Required	Description	Default
`tool_name`	Yes
`parameters`	Yes
`ttl_seconds`	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.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly reveals two key behavioral traits—'short-lived' (time-limited, aligning with ttl_seconds) and 'single-use' (one-time consumption)—which go beyond the schema. It doesn't mention side effects or prerequisites, but the disclosed traits are valuable.

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 with no filler. Every word contributes to meaning: issue, short-lived, single-use, exact, production operation.

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?

The tool has nested parameters, no annotations, and an output schema. The description explains purpose and key constraints but leaves gaps about what to put in parameters, what makes an operation 'production', and how the confirmation is consumed. Given the complexity, more context would be helpful.

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?

Schema description coverage is 0%, so the description must compensate. It hints at parameter meaning by linking 'short-lived' to ttl_seconds and 'exact production operation' to tool_name/parameters, but it doesn't specify the structure of the parameters object or how tool_name is used. Partial compensation only.

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 uses a specific verb ('issue') and resource ('confirmation') with clear qualifiers: short-lived, single-use, and for an exact production operation. This clearly states what the tool does and inherently differentiates it from sibling tools, none of which focus on issuing confirmations.

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

Usage Guidelines3/5

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

The description implies when to use the tool (when a confirmation for a production operation is needed) but provides no explicit alternatives, exclusions, or context compared to other tools like md_task_submit or ms_execute_task_request. Usage guidance is minimal but not absent.

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

Deploy Server