Skip to main content
Glama

data-api-code

curl_to_code_convert

Convert a cURL shell command into clean JavaScript fetch() or Python requests code preserving HTTP method, headers, and request body.

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

Input Schema

NameRequiredDescriptionDefault
textNo
targetNofetch

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully states the transformation is fidelity-preserving for method, headers, and body, which implies a pure local transform rather than an executed request, but it says nothing about handling of malformed or partial cURL input.

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?

A single front-loaded sentence that names the input, the two outputs, and what is preserved. No filler or redundant restatement of the tool name.

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?

For a two-parameter pure-transformation tool with no output schema and no annotations, the description covers input form, output forms, and fidelity guarantees. Missing only edge-case behavior and explicit param naming, which are minor at this complexity.

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%, so the description must compensate. It does convey the meaning of both inputs implicitly (a cURL command goes in, fetch or python is chosen as output), but it never references the parameter names 'text' or 'target', leaving the agent to map them itself; the enum values are already 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?

States a specific verb (convert) and resource (a cURL shell command) with the exact outputs produced (JavaScript fetch() or Python requests). The resource is unique among the listed siblings, so an agent can distinguish it without opening the schema.

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?

Usage is only implied by the input type: you supply a cURL command when you want equivalent code. There is no explicit when-to-use or when-not-to-use guidance, and no routing statement toward or away from alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources