Skip to main content
Glama

SVG naming signals

bpj_html_svg_labels
Read-onlyIdempotent

Inspect inline SVG elements for direct titles, ARIA names and hidden state.

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

Input Schema

NameRequiredDescriptionDefault
textYes

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, destructiveHint=false and a closed-world scope, so safety is covered. The description contributes the substantive scope (titles, ARIA names, hidden state) beyond that, but says nothing about what is reported, whether issues are flagged vs. listed, or how 'hidden state' is determined.

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 front-loaded sentence with no filler and no repetition of the title. It is efficient, but the terseness leaves the gaps noted above unfilled rather than being optimally sized for the tool's complexity.

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, annotation-covered, closed-world audit tool the description is nearly sufficient, but with no output schema the agent has no idea what the inspection returns (per-element findings, counts, issue list). One clause on the result shape would close the loop.

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?

The single 'text' parameter has 0% schema description coverage; only its title ('Source text') and maxLength=6000 hint at meaning. The description implies the input contains inline SVG but never states that the parameter expects HTML markup rather than a bare SVG fragment, which is a real ambiguity for this tool.

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 ('Inspect') and resource ('inline SVG elements') and enumerates the three signals checked: direct titles, ARIA names, and hidden state. That is enough to separate it from sibling audits like bpj_html_hidden_focusable or bpj_html_aria_reference_targets without opening a schema, though it never names 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 Guidelines3/5

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

Usage is only implied by the scope wording — an agent infers this is an SVG accessibility-naming audit. There is no explicit when-to-use statement, no prerequisites, and no guidance on when a different sibling audit is the better pick.

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.