Skip to main content
Glama

Zip JSON keys with values

bpj_json_zip_keys_values
Read-onlyIdempotent

Pair equally sized key and value arrays to form an object.

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": {
      "keys": "<keys>",
      "values": "<values>"
    },
    "name": "bpj_json_zip_keys_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYes
valuesYes

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 and repeatability need no restating. The description adds one genuine behavioral trait, the equal-size requirement, but never says what happens when sizes differ (error vs truncation) or that the inputs are JSON-encoded strings rather than plain values.

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 redundant wording or filler. It is efficient, though its brevity borders on under-specification rather than pure conciseness.

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?

With no output schema and no parameter documentation in either the schema or the description, an agent cannot tell what the returned object looks like or how failures are surfaced. For a two-parameter transform tool the definition is too thin to be called complete.

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 for both parameters and largely fails it. It only restates that keys and values are arrays; it does not explain that each parameter is a JSON array serialized as a string, nor how ordering and duplicate keys are handled, nor what effect the maxLength limits have.

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: pair key and value arrays into an object, which is more informative than the title alone. It does not explicitly distinguish this from adjacent transforms such as bpj_json_invert_string_map or bpj_json_object_defaults, so an agent must infer the boundary.

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 prerequisite conditions, and no mention of alternatives. The only usage information is implicit in the mechanics ('equally sized arrays'), which leaves the agent to guess whether this is the right tool for a given JSON reshaping task.

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.