Skip to main content
Glama

Fieldset legend review

bpj_html_fieldset_legends
Read-onlyIdempotent

Check whether each fieldset starts with a direct legend element.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 a closed-world scope, so the safety profile needs no restating. The description does add the exact criterion being tested ('direct legend'), but it says nothing about the response shape, whether one finding or all findings are returned, or how non-conforming nesting is reported.

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 filler, well matched to a single-rule checker. It is efficient, though its brevity shades into under-specification rather than tight completeness.

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?

With no output schema, the definition should say what the check returns (violations list, boolean, count) and whether it evaluates all fieldsets in the supplied text. For a one-parameter read-only auditor that is a modest but real omission.

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?

Only one parameter ('text') exists and schema description coverage is 0%, so the description carries little of the burden but also adds nothing: it never says the input is the HTML source text to be inspected, nor what the 6000-character limit implies. The parameter title 'Source text' supplies minimal meaning, leaving a small compensating 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?

States a specific verb and rule: 'Check whether each fieldset starts with a direct legend element.' The resource (fieldset/legend) is named precisely, which implicitly separates it from sibling checks like table caption or th scope, though it never names an alternative explicitly.

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 stated prerequisites, and no alternatives or exclusions. The usage is only inferable from the rule itself (an accessibility lint over HTML source), which is the level of guidance the MID calibration example scored as 2.

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.