Skip to main content
Glama

Remove null-valued object members

bpj_json_remove_null_members
Read-onlyIdempotent

Recursively remove object fields containing null while retaining array positions.

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": {
      "document": "<document>"
    },
    "name": "bpj_json_remove_null_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description still adds real behavioral value by disclosing recursion and the array-position preservation rule, which determines the output shape. It does not say what happens to invalid JSON input or whether the result is returned as text.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single ten-word sentence that front-loads the operation and appends the one nuance that matters. Nothing is wasted and no re-reading is required.

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?

For a one-input, non-destructive, annotation-backed utility, the description covers what is transformed and an important edge case (array nulls preserved). The only remaining gap is input-validity and output-format behavior, which is minor given there is no output schema to explain.

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?

With a single parameter and 0% schema description coverage, the description supplies no information about the document argument at all. The schema itself carries type string, title "JSON document", required, and maxLength 6000, which is enough to call the tool, but nothing clarifies encoding, validity requirements, or size behavior.

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 ("Recursively remove object fields containing null") plus a scope qualifier ("retaining array positions"), so the transformation is unambiguous. It does not reference a sibling such as bpj_json_null_locations, so the agent must infer the distinction between removing nulls and locating them.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the phrase "remove object fields containing null" scopes the operation to object members only, and "retaining array positions" signals that nulls inside arrays are untouched. There is no explicit when-to-use, when-not-to-use, or named alternative guidance.

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.