Fortran Companion MCP Server

by enkiEng

Overview Schema Source Related Servers Discussions Admin

Python

Local

compile_project

Automatically detects and runs fpm build or make to compile Fortran projects based on their layout.

Instructions

Compiles the Fortran project. Automatically detects and runs 'fpm build' or 'make' depending on layout.

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": {
      "project_path": "<project_path>"
    },
    "name": "compile_project"
  }
}

Input Schema

Name	Required	Description	Default
`project_path`	Yes	The path of the project.
`fortran_version`	No	The Fortran standard version to enforce (e.g. 'f95', 'f2003', 'f2008', 'f2018', 'f2023'). Defaults to 'f2018'.	f2018

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations provided, so description is the only source. Mentions automatic build system detection, but lacks details on failure handling, side effects, or output location.

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?

Two concise sentences, front-loaded with core action, no unnecessary words.

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?

Complete enough given schema and output schema exist, but could mention that compilation produces a binary or typical output location.

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 already fully describes both parameters (100% coverage). Description adds no extra semantic meaning beyond what's in the schema.

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?

Clearly states verb (compiles), resource (Fortran project), and adds behavior (auto-detects fpm build or make). Distinguishes from siblings which are analysis, formatting, or testing tools.

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?

No explicit guidance on when to use this tool vs alternatives. Does not mention prerequisites or when not to use.

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