Skip to main content
Glama

Progress element states

bpj_html_progress_states
Read-onlyIdempotent

Distinguish indeterminate progress elements and validate positive maxima and bounded values.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, closed-world), so the description does not need to re-establish that. It adds genuine check semantics — what conditions are inspected — but says nothing about the volume of findings, how violations are surfaced, or edge cases like a value with no max.

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 tight sentence with zero filler, front-loading the two behaviors (indeterminate detection, then max/bounds validation). It is efficient, though the compression leaves key details unspoken rather than being genuinely complete.

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 one required input and no output schema, the description should clarify whether the tool returns findings, booleans, or rewritten markup, and whether the input is a full document or a fragment — none of which is stated. It covers the essential intent well enough to call the tool, but leaves the return contract entirely implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter exists and the schema fully constrains it: a required 'text' string of source text capped at 6000 characters, with additionalProperties=false. The description cannot add much beyond confirming this, and there is no ambiguity about what the input is.

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 resource (progress elements) and two concrete checks: detecting the indeterminate state (no value) and validating that maxima are positive and values stay bounded. That is well beyond a restatement of the title 'Progress element states'. It stops short of naming any sibling, so an agent must infer on its own that bpj_html_meter_range_check is the near analogue for <meter>.

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 statement of when to reach for this tool, no prerequisite (e.g. the HTML source must contain <progress> elements), and no exclusion or alternative offered. The phrasing implies an accessibility/validity audit context, but the agent gets no routing guidance.

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.