Skip to main content
Glama

Fill missing config defaults

bpj_json_object_defaults
Read-onlyIdempotent

Fill absent top-level config keys and preserve explicit null values.

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

Input Schema

NameRequiredDescriptionDefault
objectYes
defaultsYes

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, so the safety profile is covered. The description still adds real behavior: only absent keys are filled, existing keys are untouched, and explicit nulls are not treated as absent. It omits that inputs are JSON-encoded strings, precedence rules, and handling of malformed JSON.

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?

One tight sentence with the key qualifiers ('absent', 'top-level', 'preserve explicit null') front-loaded and no filler. It is efficient but arguably too terse for a zero-coverage schema.

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?

Reasonable for a two-parameter pure function, and annotations cover the safety profile. However, with no output schema the description never indicates what is returned (merged object as JSON text?), and error behavior for non-object or invalid JSON input is unaddressed.

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% — both parameters carry only titles ('JSON object', 'Default object') with no semantics. The description hints that 'defaults' supplies absent keys but never states precedence (object wins), that both are serialized JSON strings, or what an invalid value does. It does not compensate for the coverage gap.

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: fill absent top-level config keys, while preserving explicit nulls. The 'top-level' and 'absent' qualifiers scope the operation and differentiate it from deeper-merge siblings, though no sibling is named explicitly.

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?

Implies the use case (hydrating a config with defaults) via the wording 'config keys', and the 'top-level' qualifier implicitly excludes deep merges. But there is no explicit when-to-use/when-not statement and no pointer to bpj_apply_json_merge_patch for nested needs.

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.