Skip to main content
Glama
Sign In
tool-mcp-server

tool-mcp-server

by maple-awa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tool_string_to_file

Convert string content into a file with a specified filename. Use this tool to generate files programmatically.

Instructions

[data] String To File

Parameters:

  • content (string): Content

  • filename (string): Filename

Outputs:

  • file (bytes): File

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

Input Schema

NameRequiredDescriptionDefault
fileNoFile (base64 file payload)
contentNoContent
filenameNoFilename

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior1/5

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

The description claims the output is 'file (bytes)' while the input schema defines 'file' as an object with base64 fields, creating a mismatch. With no annotations, the description fails to accurately disclose the output behavior and also omits the 'file' input parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and structured with headings, but the '[data]' prefix and redundant parameter list add little value. It is adequately concise but not exemplary.

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?

The tool has a nested object and no output schema, yet the description provides no clarification about the file object structure or the optional file input, leaving the tool's actual behavior ambiguous.

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

Parameters2/5

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

The schema has full descriptions for content and filename, but the description omits the 'file' parameter listed in the schema and adds no semantic detail beyond the schema's terse descriptions.

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?

The description clearly indicates the tool converts a string to a file, listing content and filename as inputs. It distinguishes from sibling tool_file_to_string, though it doesn't explicitly name an alternative.

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?

No explicit guidance on when to use this tool or alternatives. The name implies usage, but there is no direct comparison with sibling tools like tool_base64_to_file or tool_file_to_string.

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

Deploy Server

Other Tools