Skip to main content
Glama

Deduplicate structured array values

bpj_json_array_unique_values
Read-onlyIdempotent

Keep the first occurrence of each structurally equal array value.

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": {
      "array": "<array>"
    },
    "name": "bpj_json_array_unique_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
arrayYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this as a safe, read-only, idempotent, non-destructive operation. The description adds the important tie-breaking behavior (first occurrence wins) and structural equality, but it does not explain return format, invalid-input behavior, or the max-length constraint.

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?

The description is a single front-loaded sentence with no filler. Every phrase carries semantic weight about the deduplication rule.

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 simple one-parameter tool with no output schema, the description should at least clarify input encoding and return behavior. Annotations cover safety, but the missing input-format detail is critical because the schema only says string.

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%, and the single parameter is typed as a string with maxLength 5000. The description references array values conceptually but never states that the parameter must be a JSON-encoded array string or how malformed JSON is handled, so it does not compensate for the schema 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?

The sentence states a specific rule: keep the first occurrence of each structurally equal array value. That makes the deduplication behavior clear and distinguishes it from line-based deduplication, though it never explicitly says it returns a deduplicated array or that the input is JSON text.

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 or when-not-to-use guidance, and no mention of alternatives such as bpj_deduplicate_lines. Usage is only implied by the deduplication rule.

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.