Skip to main content
Glama

Positive tabindex review

bpj_html_positive_tabindex
Read-onlyIdempotent

Locate positive integer tabindex values for a keyboard navigation order review.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 the safety profile needs no restating. The description adds only the framing that this is a detection pass rather than a fix; it says nothing about what happens to text exceeding maxLength 6000 or whether matches are reported with positions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the verb and the artifact being searched, with zero filler. Nothing in it is redundant with the title or the annotations.

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?

For a one-parameter read-only detector with annotations covering the safety profile, the definition is nearly sufficient. The one meaningful gap is that there is no output schema, so the agent has no signal about whether the result is a count, a list of offending values, or their locations in the source.

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 single 'text' parameter is documented only by its title 'Source text' and a 6000-character cap. The description hints that the input is HTML markup by talking about tabindex values, but it never states that the caller supplies raw HTML source rather than a URL or element list.

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 pairs a specific verb ('Locate') with a precise resource ('positive integer tabindex values') and names the review it feeds ('keyboard navigation order review'). An agent can tell this apart from siblings like bpj_html_autofocus_review or bpj_html_accesskey_conflicts from the resource alone, though it never explicitly contrasts them.

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 a keyboard navigation order review' implies the context in which to reach for this tool, but there is no statement of when not to use it and no named alternative. Usage is inferable rather than prescribed.

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.