Skip to main content
Glama

Expand dotted config keys

bpj_json_dot_keys_nest
Read-onlyIdempotent

Nest dotted root keys into objects and reject colliding paths.

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>"
    },
    "name": "bpj_json_dot_keys_nest"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectYes

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 readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds one genuinely useful behavioral fact — colliding paths are rejected rather than merged — but says nothing about whether rejection aborts the whole transform or how the error surfaces.

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 filler — the transform and its collision rule come first. It is terse to the point of under-specification, but nothing is wasted.

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 transform tool with no output schema and an undocumented sole parameter, the description should say what comes back (nested JSON?) and what a collision looks like. Neither is covered, leaving real ambiguity an agent cannot resolve from structured fields.

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?

With one required parameter at 0% schema description coverage, the description must carry the load, but it never explains that `object` is a JSON object serialized as a string (max 6000 chars) nor what key syntax is expected. 'Dotted root keys' hints at input shape but does not document the parameter itself.

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 gives a specific verb and resource: nesting dotted root keys into objects, plus a stated edge-case behavior (rejecting colliding paths). An agent can tell this is a key-restructuring transform, though it does not name or contrast any sibling such as bpj_json_retain_root_keys or bpj_flatten_json.

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 guidance, no prerequisites, and no mention of alternatives among the many JSON-transformation siblings. Usage is only implied by the described transformation.

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.