Skip to main content
Glama

Project root object keys

bpj_json_retain_root_keys
Read-onlyIdempotent

Select requested root fields and identify absent ones.

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

Input Schema

NameRequiredDescriptionDefault
keysYes
objectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds one genuine piece of behavioral context beyond that — that absent keys are identified rather than silently dropped — but says nothing about output shape, ordering, or how nested keys are handled.

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 or repetition. It is efficient, though its brevity arguably costs clarity on what the returned 'absent ones' look like.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining the result, and 'identify absent ones' is vague about whether absences appear as a separate list, a flag, or omitted members. For a two-required-parameter JSON transformation tool this is adequate but not fully complete.

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%; the only structured help is the property titles ('JSON array of field names', 'JSON object'). The description partially compensates by tying 'keys' to 'requested root fields' and scoping the operation to root level, but it never clarifies that both parameters are JSON-encoded strings with character limits.

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 names a specific verb and resource: select requested root fields from a JSON object and report which were absent. That is enough to distinguish it from mutating siblings like bpj_json_rename_root_key or bpj_json_redact_field, though it does not explicitly contrast with similar retaining/defaulting tools such as bpj_json_object_defaults.

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 explicit when-to-use guidance, no prerequisites, and no named alternative for cases where nested keys or default filling are wanted. The use case is only weakly implied by 'Select requested root fields', leaving the agent to infer the scenario.

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.