Skip to main content
Glama

Field mapping and renaming module with pytest tests

submit_field_mapping
Idempotent

Produce a standard-library Python module that renames and selects JSON fields using a mapping, plus pytest tests. Choose this when fields must be renamed and selected via an explicit source-to-destination mapping. Do not choose this for computed or transformed values: only names and selection change. Example requests: Write a Python module that renames and selects JSON fields using a mapping, with tests. | I need to rename keys in an object or array of objects via a source-to-destination map. | Generate a field-mapping module and test it.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_field_mapping"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful artifact detail (standard-library module plus pytest tests) and a constraint that only names/selection change, but it does not disclose the authorization/pricing workflow implied by quote_id and accepted_price.

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 purpose and usage guidance are front-loaded and easy to scan. The three example requests are somewhat repetitive but useful for matching user phrasing, so the description is appropriately sized rather than bloated.

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?

With annotations and an output schema present, the description covers what to generate, when to choose it, and what not to use it for. The main gap is that it does not mention the quoted-job authorization flow, though the schema partially documents quote_id and accepted_price.

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 75%, and the schema already documents module_name, function_name, template, quote_id, and accepted_price. The description adds no parameter-level meaning beyond the schema and does not clarify authorized_by, but it does not need to restate well-covered schema details.

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 uses a specific verb and resource: produce a standard-library Python module that renames and selects JSON fields using a mapping, plus pytest tests. It also scopes the behavior by excluding computed or transformed values, which distinguishes it from transformation-oriented siblings even though none are named.

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

Usage Guidelines4/5

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

It gives explicit when-to-use guidance ('Choose this when fields must be renamed and selected via an explicit source-to-destination mapping') and when-not-to-use guidance ('Do not choose this for computed or transformed values'). It does not name a specific alternative tool, which keeps it short of a 5.

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