Skip to main content
Glama

Radio group defaults

bpj_html_radio_group_defaults
Read-onlyIdempotent

Group static radio inputs by form owner and name to detect multiple checked defaults and empty names.

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": {
      "text": "<text>"
    },
    "name": "bpj_html_radio_group_defaults"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

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, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds real behavioral value by stating the grouping key (form owner + name) and the two findings reported (multiple checked defaults, empty names). It does not disclose output shape, how malformed or unclosed markup is handled, or the effect of the 6000-character input cap.

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?

One compact sentence with the action front-loaded and no filler; every clause (grouping key, static scope, both detections) carries information. It is arguably too terse given the missing input and output detail, but the sentence itself is well built.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a single-parameter analyzer with full annotation coverage and no output schema, so the bar is modest, and the description covers the grouping logic and the findings produced. The remaining gap is input semantics — what exactly 'text' should contain — which is the one thing an agent still has to guess.

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% for the single 'text' parameter, so the description must compensate and it does not — it never mentions that the input is the HTML source to scan or what forms of markup it expects. The reader must infer from the tool name that a radio-bearing HTML fragment is required.

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 uses a specific verb-and-resource pairing ('Group static radio inputs by form owner and name') and adds a concrete outcome ('detect multiple checked defaults and empty names'). An agent can tell what it produces without opening the schema, though it does not name or distinguish itself from any sibling HTML-review tool.

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 word 'static' signals that dynamically injected radios are out of scope, and the detection targets suggest an HTML/accessibility audit context. There is no explicit when-to-use statement, no prerequisite, and no routing to or away from alternatives such as the other bpj_html_* review tools.

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.