Skip to main content
Glama

Form label consistency

bpj_form_label_check
Read-onlyIdempotent

Compare a field’s visible label with its accessible name and check required-state consistency.

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": {
      "visible": "<visible>",
      "accessible": "<accessible>",
      "visiblyRequired": "<visiblyRequired>",
      "programmaticallyRequired": "<programmaticallyRequired>"
    },
    "name": "bpj_form_label_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
visibleYes
accessibleYes
visiblyRequiredYes
programmaticallyRequiredYes

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?

The annotations already declare readOnly, idempotent, closed-world, and non-destructive behavior, so the safety profile is covered without the description's help. The description adds only a light hint that two pairwise comparisons occur; it says nothing about what 'compare' tolerates (case, whitespace, non-breaking spaces, truncation) or what verdict is produced. For a pure-check tool with rich annotations, this is adequate but thin.

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 sentence, front-loaded with the primary comparison and with zero filler. Slightly compressed to the point that the two distinct checks run together without a break, but nothing 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?

The tool is simple and fully-required, and annotations cover its safety profile. However, with no output schema, the description leaves the return value entirely unknown — an agent cannot tell whether it receives a boolean, a list of mismatches, or a severity verdict, which matters for a check tool meant to feed an audit.

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 description coverage is 0%, so the description must carry the load, and it partially does by grouping the four parameters into two comparison pairs (label comparison, required-state comparison). It does not explain how blank strings are treated, which the schema title flags with '(may be blank)' but never resolves into rules. Baseline-plus for mapping parameters to the two checks, not enough for a 4.

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 ('Compare') and resource ('a field's visible label' vs 'accessible name') plus a second check ('required-state consistency'). The word 'field's' scopes it away from the sibling link/image label checkers, though it does not name 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the phrase 'a field's visible label' — an agent can infer this is for auditing form-field accessibility. There is no explicit when-to-use statement, no exclusions, and no pointer to related siblings such as bpj_link_label_check for other control types.

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.