Skip to main content
Glama

api_synthesizer

Converts raw cURL commands into a fully typed Python client SDK, turning captured network traffic into reusable client code.

Instructions

Reverse-engineers raw cURL network traffic into a fully typed Python client SDK.

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": {
      "curl_command": "<curl_command>"
    },
    "name": "api_synthesizer"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_nameNoApiClient
curl_commandYesRaw cURL string

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden yet says nothing about execution behavior: whether the cURL is replayed over the network or only statically parsed, whether generated files are written to disk or returned inline, how credentials embedded in the cURL are handled, or what happens on unsupported syntax. The phrase 'fully typed' is an unverifiable quality claim rather than behavioral information.

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?

A single well-formed sentence with the input-to-output transformation front-loaded and no filler. Slight deduction for promotional wording ('fully typed') in place of concrete detail.

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?

For a two-parameter tool with no output schema and no annotations, the description is far too thin: an agent cannot tell whether the SDK is returned as a string, persisted to disk, or streamed, nor what a successful versus failed parse looks like. It also omits the second parameter entirely, leaving a real gap relative to the tool's complexity.

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?

Schema coverage is only 50%, and the description supplies no parameter detail at all. The 'curl_command' parameter is at least echoed by the word 'cURL', but 'client_name' is never mentioned, so the description cannot compensate for the undocumented half of the schema — an agent gets no hint that it names the generated Python class or how it affects output.

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?

States a specific verb ('Reverse-engineers'), a concrete input ('raw cURL network traffic') and a concrete artifact ('fully typed Python client SDK'), so the transformation is unambiguous. It earns no fifth point because it never positions itself relative to any alternative approach, and the sibling list gives no clue how it relates to tools like blackbox_cloner or token_squeezer.

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?

There is no when-to-use framing, no prerequisites, and no statement about what kinds of cURL invocations are acceptable (authenticated, multipart, GraphQL, etc.). The only usage signal is implicit in the transformation described, which leaves the agent guessing about applicability.

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