mort-mcp

Overview Schema Source Related Servers Discussions Admin

mort_run

Compile Mort source to a native binary and execute it with optional stdin, arguments, and timeout, capturing program output and compile errors.

Instructions

Compile Mort code to a native binary and run it, capturing its output.

Needs a C compiler (cc/gcc/clang, or pip install ziglang). stdin is fed to the program, args are its command-line arguments, and it is killed after timeout_s. Reports compile errors the same way mort_check does.

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": "mort_run"
  }
}

Input Schema

Name	Required	Default
`args`	No
`files`	No
`stdin`	No
`source`	No
`opt_level`	No	0
`timeout_s`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.8/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 and does well: it discloses the external C-compiler dependency and the pip install ziglang fallback, that stdin is piped in, args are passed as command-line arguments, and the process is killed after timeout_s. It leaves out whether/where a binary artifact is written and any sandbox or filesystem side effects, which keeps it short of a 5.

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?

Four sentences, front-loaded with the purpose, then prerequisites, then runtime parameter behavior. No filler, though the parameter explanations are packed into one long sentence rather than structured.

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, and the compiler prerequisite plus process-control behavior are covered. Still, three parameters and the question of whether a binary is persisted to disk are unaddressed, which matters for a tool that both compiles and executes code.

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 six parameters, so the description must compensate, and it only does so for three of them: stdin, args and timeout_s are explained in prose. The meaning of files, source and opt_level (including valid opt_level values) is left entirely to bare schema titles and defaults.

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 specific compound verb and resource: compile Mort code to a native binary and run it, capturing output. The mention that compile errors are reported 'the same way mort_check does' implicitly separates it from the check-only and emit-C siblings.

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 makes it clear this is the execution path when you need to observe program output, stdin, args or timeouts. However, it never explicitly says when to prefer mort_check or when not to use this tool (e.g. avoid when no C compiler is available, even though a fallback via ziglang is mentioned).

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

Deploy Server