Kratos MCP Server

Overview Schema Source Related Servers Discussions Admin

mdpa_set_table

Create or replace a piecewise-linear time series table in MDPA files by defining variables (e.g., TIME vs VELOCITY) and [x,y] row data.

Instructions

Create or replace a top-level 'Begin Table <x_variable> <y_variable>' block (piecewise-linear time series, e.g. TIME vs VELOCITY); rows are [x, y] pairs.

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>",
      "table_id": "<table_id>",
      "x_variable": "<x_variable>",
      "y_variable": "<y_variable>",
      "rows": "<rows>"
    },
    "name": "mdpa_set_table"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`rows`	Yes
`output`	No
`table_id`	Yes
`overwrite`	No
`x_variable`	Yes
`y_variable`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.9.0Oct 16, 2026

TDQS

B3.2/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 the upsert nature ('Create or replace') and that the block is top-level, but says nothing about permissions, what happens to file contents, or the interaction with the separate 'overwrite' parameter (default false), which arguably conflicts with the 'replace' wording.

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 dense sentence, front-loaded with the action verb, with no filler. Slightly dense given the nested quoted block syntax, but every clause carries information.

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?

An output schema exists, so return values need not be described. But for a 7-parameter mutation tool with no annotations and 0% schema coverage, the description leaves overwrite semantics, the meaning of path/output, and error behavior on an existing table unaddressed.

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 explains rows as '[x, y] pairs' and clarifies x_variable/y_variable through the block syntax, adding real value beyond the bare schema. However, path, output, and overwrite are left entirely unexplained.

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 and resource ('Create or replace a top-level Begin Table block') and defines what the resource is (piecewise-linear time series, e.g. TIME vs VELOCITY), so an agent can tell this is a table-writing tool. It does not explicitly differentiate itself from siblings like mdpa_delete_table or mdpa_set_nodal_data, keeping it at a 4 rather than a 5.

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?

The description defines the artifact but gives no when-to-use guidance, no prerequisites, and does not name alternatives such as mdpa_delete_table or mdpa_get_data_blocks. An agent must infer the usage context entirely from the resource definition.

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

Deploy Server