docuwriter

Convert Source Code Language

generate-language-conversion

Use this when the user supplies one source-code file and asks to convert it to another programming language or framework. After authorization, this state-changing action consumes AI credits, creates a generation, and returns converted code using source_code, filename, from_language, and to_language.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Optional generation history name for the converted output. Defaults to the supplied filename when omitted.
`filename`	Yes	Filename for the supplied source code, including extension when known, so the generator can name the generation and understand context.
`source_code`	Yes	Source code contents to convert. Use this only when the customer supplied the code text to the MCP client; use browser guidance for local file picker uploads.
`to_language`	Yes	Target programming language or framework to convert to, such as TypeScript, Python, Go, Vue, TailwindCSS, CSS, or Laravel.
`from_language`	Yes	Source programming language or framework to convert from, such as PHP, JavaScript, Python, React, Bootstrap, CSS, or Laravel.
`save_to_space`	No	Optional destination Space item for saving the converted code after authorization. The authenticated user must be able to manage that Space.
`additional_instructions`	No	Optional conversion guidance, such as preserving APIs, using a framework version, matching style conventions, or focusing on compatibility.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description discloses important side effects: it is state-changing, consumes AI credits, creates a generation, and returns converted code. It could be more explicit about save_to_space behavior, but the parameter description covers that. No contradiction with annotations.

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?

The description is a single sentence and reasonably concise, but it redundantly lists parameter names at the end ('using source_code, filename, from_language, and to_language') which does not add much value.

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

Completeness4/5

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

Given there is no output schema, the description adequately states that the tool returns converted code and mentions key side effects like credit consumption and generation creation. It does not detail response structure, but that is not critical for invoking the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All seven parameters have schema descriptions, and the tool description reinforces some by naming key parameters. The parameter descriptions provide useful examples and usage conditions, though 'name' and 'source_code' could be slightly clearer.

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 a specific use case: converting a user-supplied source-code file to another programming language or framework. This distinguishes it from sibling tools that generate documentation, comments, tests, or other code artifacts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit guidance on when to use the tool ('when the user supplies one source-code file and asks to convert it'). This is sufficient to route the agent correctly among many similar code-generation tools.

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

All docuwriter tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?