Skip to main content
Glama

Build an RFC 7464 JSON text sequence

bpj_json_text_sequence
Read-onlyIdempotent

Frame each member of a JSON array with an ASCII record separator and line feed for RFC 7464 interchange.

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": {
      "records": "<records>"
    },
    "name": "bpj_json_text_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real format detail beyond annotations by naming the exact delimiter pair (ASCII record separator plus line feed), but says nothing about the return shape or how the framed output is delimited as a whole.

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 wasted words; the action, input, delimiters, and standard all arrive in one pass. It is appropriately sized for a narrow pure-transformation tool.

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 one-parameter, side-effect-free formatter with no output schema, the description covers the core mechanics, but it leaves the caller unsure whether the result is a string, whether a trailing terminator is emitted, or how the 6000-character limit is enforced.

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?

There is a single required parameter with 0% schema description coverage, so the description must carry the load. Saying "each member of a JSON array" does clarify that the input is an array whose elements are framed one by one, which matches the "JSON array of records" parameter, but it never addresses that the value is a string with a 6000-character cap.

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 names a specific verb ("Frame") and resource ("each member of a JSON array"), plus the target standard RFC 7464, so the transformation is unambiguous. It does not distinguish itself from siblings like bpj_check_json_lines or bpj_json_feed_channel, but the core action is clear.

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?

The phrase "for RFC 7464 interchange" implies when this is appropriate, but there is no explicit guidance on when to use this versus alternatives, no prerequisites, and no statement about which inputs are unsuitable.

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.