Kratos MCP Server

Overview Schema Source Related Servers Discussions Admin

mdpa_set_properties

Modify a Kratos MDPA file's mesh-embedded 'Begin Properties' block: add, replace, or remove values for a property ID, or update the 'ModelPartData' header.

Instructions

Edit the mesh-embedded 'Begin Properties' block of one property id (values {"DENSITY": 7850.0} are added/replaced, 'remove' deletes names; lists are written space separated) and/or the 'ModelPartData' header. Most cases keep material data in Materials.json instead -- see materials_set_property.

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": {
      "path": "<path>"
    },
    "name": "mdpa_set_properties"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`output`	No
`remove`	No
`values`	No
`overwrite`	No
`property_id`	No
`model_part_data`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.9.0Oct 16, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations the description carries the full burden. It usefully discloses that values are added/replaced, 'remove' deletes names, and lists are written space separated, but it does not explain the 'overwrite' flag, the 'output' parameter, or what happens when property_id is null — all material for a mutation tool.

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?

Two sentences, action front-loaded and the alternative-pointer placed last. The dense parenthetical packing value format and remove semantics is a little hard to parse but every clause earns its place.

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?

Return values are covered by the output schema, so they need not be explained. However, for a 7-parameter mutation tool with no annotations and 0% schema coverage, leaving overwrite/output semantics undocumented is a real gap given the tool's complexity.

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% across 7 parameters, so the description must compensate. It explains the value format, remove semantics, and implicitly ties property_id/model_part_data to the two blocks, but leaves 'overwrite', 'output', and 'path' unaddressed, so compensation is only partial.

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 concrete verb ('Edit') and resource (the mesh-embedded 'Begin Properties' block of one property id and/or the 'ModelPartData' header), so the agent knows exactly which block is touched. It also distinguishes itself from the sibling materials_set_property, though it does not differentiate from other mdpa_set_* tools.

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?

Explicitly routes the agent away from this tool in the common case: 'Most cases keep material data in Materials.json instead -- see materials_set_property.' That is a clear when-not plus a named alternative, but no guidance is given for choosing among the other mdpa_set_* siblings.

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

Deploy Server