Skip to main content
Glama

Profile JSON record fields

bpj_profile_json_records
Read-onlyIdempotent

Summarize field presence, missing values, nulls and observed types in a sample of JSON records.

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": {
      "json": "<json>"
    },
    "name": "bpj_profile_json_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
jsonYes

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 establish this as a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is fully covered. The description adds that the result is a summary of observed characteristics over a sample rather than a transformation or validation verdict, which is useful. It does not say how many records constitute the sample, whether input must be an array or NDJSON, or what the summary output looks like.

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 sentence, front-loaded with the verb and the enumerated outputs, with no filler or restatement of the tool name. Every clause contributes a distinct fact about what is reported.

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?

For a simple single-parameter read-only tool this is close to adequate, and annotations handle the safety story. But with no output schema, the description should at minimum sketch the shape of the returned report (per-field counts, type lists, null rates) so an agent knows what to expect; that is missing, as is any note on input size limits.

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?

Schema coverage is 0%, so the description carries the burden, and it only partially does: the phrase "a sample of JSON records" implies the single `json` string holds multiple records rather than one object, which is meaningful added context. However, it never clarifies the accepted encoding (array vs. JSON Lines) nor warns about the 12000-character maxLength, leaving format ambiguity unresolved.

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 ("Summarize") and a precise set of reported facts: field presence, missing values, nulls and observed types. The resource is identifiable as JSON records, and the name/title pairing makes it distinct from bpj_profile_csv and from transformation siblings like bpj_flatten_json or bpj_format_json, though the description itself does not name an alternative.

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 mention of when a different tool (e.g. bpj_check_json_lines for validation or bpj_compare_json for diffs) would be the better choice, and no stated prerequisites. The word "sample" is the only contextual hint, and it is left unexplained.

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.