Skip to main content
Glama
enkiEng

Fortran Companion MCP Server

by enkiEng

format_code

Format Fortran code with configurable indentation and line length using fprettify to enforce consistent styling.

Instructions

Auto-formats a string of Fortran code using fprettify to enforce modern indentation and spacing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesThe Fortran code content to format.
indentNoRelative indentation width (default: 3).
line_lengthNoColumn after which a line should end (default: 132).
whitespaceNoPreset (0-4) for the amount of whitespace (default: 2).
strict_indentNoStrictly impose indentation even for nested loops (default: False).
enable_declNoEnable whitespace formatting of declarations (default: False).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description must fully disclose behavior. It only mentions formatting but does not state whether it is read-only, if syntax errors are handled, or any side effects.

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?

Single sentence, front-loaded with the verb and purpose, with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite output schema existing, the description is minimal for a tool with 6 parameters. It does not mention installation requirements, error handling, or whether the input code is modified in place.

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 has 100% description coverage, so baseline is 3. The description adds no additional meaning beyond what the schema provides.

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?

The description clearly states the verb 'auto-formats' and the resource 'string of Fortran code', using the specific tool fprettify. It distinguishes from sibling tool 'format_file' which likely operates on files.

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 guidance on when to use this tool vs alternatives like format_file or lint_code. The description does not specify prerequisites or context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/enkiEng/fortran-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server