Skip to main content
Glama

Rename a root object key

bpj_json_rename_root_key
Read-onlyIdempotent

Rename a top-level key after checking the source and destination.

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": {
      "object": "<object>",
      "field": "<field>",
      "target": "<target>"
    },
    "name": "bpj_json_rename_root_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYes
objectYes
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds only the hint that source and destination are validated before the rename, without saying what the check is or what happens on failure (missing source key, target already existing, invalid JSON input).

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 front-loaded sentence with no wasted words; nothing redundant is present. It is arguably too terse for the gaps it leaves, but structurally clean.

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 3-required-parameter transformation with no output schema and no annotations about output format, the description omits key behavior: whether the original key is removed, whether ordering is preserved, and how errors surface. Too thin to call the tool confidently on edge cases.

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 description coverage is 0%, so the description carries the burden, yet it never explains the three parameters. 'Source' and 'destination' loosely map to 'field' and 'target', but 'object' (the JSON string, max 6000 chars) and the exact matching rules for 'field' are left entirely to the bare schema titles.

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 and resource ('Rename a top-level key') and scopes it to the root of the object, which separates it from nested-key manipulation siblings like bpj_json_dot_keys_nest. It does not name a sibling alternative or clarify what 'top-level' means for arrays/nested objects.

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 guidance on when to choose this over the many other JSON transformation siblings, and no stated prerequisites beyond the vague 'after checking' clause. The agent must infer that this is the right tool for renaming a single root key.

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.