Skip to main content
Glama

Inventory JSON strings

bpj_json_string_inventory
Read-onlyIdempotent

List string values and their pointers, retaining repeated occurrences.

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_string_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely behavioral fact beyond that — duplicates are kept, not collapsed. It does not say whether traversal reaches nested structures, how pointers are formatted, or in what order results appear.

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?

One short clause with the distinguishing behavior front-loaded after the core action; there is no filler, hedging, or redundancy. Nothing in it is wasted.

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?

This is a simple read-only tool with one parameter and no output schema, so the description does not need to explain return values in depth. Still, for a tool whose entire output is "pointers" and whose only input is a raw JSON string of bounded length, the absence of any pointer-format or input-handling detail leaves a real gap.

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?

The single parameter has 0% schema description coverage, and the description never mentions the document input at all — no statement that it must be a JSON document, no note about the 6000-character limit or what happens on invalid JSON. With low coverage the description was expected to compensate and does not.

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?

"List string values and their pointers" gives a specific verb and two concrete resources, and "retaining repeated occurrences" distinguishes it from dedupe-style siblings such as bpj_json_array_unique_values. It stops short of naming an explicit alternative, but the operation is unambiguous.

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 only implied: the phrase "retaining repeated occurrences" signals it is the non-deduplicating inventory variant, which is a useful routing cue against unique-value tools. There is no explicit when-to-use, when-not-to-use, or named alternative, so an agent must infer fit from context.

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.