Skip to main content
Glama
Sign In
Kratos MCP Server

Kratos MCP Server

by loumalouomega
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

materials_check

Validate a single-stage Kratos case by checking Materials.json against its mesh: verify model part names, used properties IDs, and constitutive laws, importing listed applications first.

Instructions

Cross-check a case's Materials.json against its mesh: every entry's model_part_name must be the root model part or one of the mesh's sub model parts, every properties_id used by an element needs an entry, and (with a Kratos build) every constitutive law must exist -- pass the application names that register them (e.g. ["StructuralMechanicsApplication"]) so they are imported first. Single-stage cases 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": {
      "parameters_file": "<parameters_file>"
    },
    "name": "materials_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationsNo
parameters_fileYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations, so the description must carry the behavioral load, and it does well: it discloses the three concrete checks, the dependency on a Kratos build, the ordering side-effect of importing applications first, and the single-stage restriction. It is silent on failure/reporting behavior, but the output schema covers results.

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?

One dense sentence, but the checks and the applications guidance are front-loaded with the exclusion at the end. The em-dashes and parenthetical add useful specifics rather than padding, though the clause stacking is heavier than ideal.

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 an output schema present, return values need no explanation, and the description fully covers the check semantics plus the single-stage caveat. The only gap is the undocumented parameters_file argument, which is minor given its self-describing name.

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 coverage is 0%, so the description must compensate. It explains the 'applications' parameter thoroughly, including format and a concrete example (["StructuralMechanicsApplication"]), but says nothing about 'parameters_file' beyond what its name implies. Half the parameters are clarified, so it is only partially compensatory.

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?

States a precise verb (cross-check) and the two resources being reconciled (Materials.json against the mesh), then enumerates the exact invariants verified. This separates it cleanly from siblings like materials_get, materials_set_property, and mdpa_validate without opening any schema.

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?

Gives clear context for invocation (pass application names so constitutive laws are imported first) and an explicit exclusion ('Single-stage cases only'). It does not name a specific alternative tool like validate_case or mdpa_validate, so it stops short of full when/when-not routing.

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

Deploy Server

Other Tools