Skip to main content
Glama

Details summary check

bpj_html_details_summaries
Read-onlyIdempotent

Report direct summary counts and the first child element of each details panel.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. Beyond that the description adds no behavioral context: it does not say how it treats malformed HTML, whether a details element with no summary is flagged or errored, or whether the input is parsed or truncated at the schema's maxLength.

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 two things reported and with no filler or hedging. It is efficient and appropriately sized for a narrow single-input check. The only cost is that terseness edges into ambiguity.

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?

There is no output schema, so the description carries responsibility for the return shape, and it only partly delivers: "direct summary counts" could mean one aggregate number or a per-panel count, and "first child element" is undefined for empty panels. For a single-parameter, read-only checker this is roughly minimally adequate, but an agent cannot predict the response structure.

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

Parameters2/5

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

There is a single required parameter with 0% schema description coverage (only the title "Source text" and a maxLength are given). The description implies the input is HTML markup containing details panels but never states that explicitly, nor does it mention the 6000-character limit or what happens at the boundary. With one parameter the burden is light, but the description still does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete verb ("Report") and a narrow resource (summary counts and the first child element of each details panel), which gives an agent a rough idea of the check. But "details panel" is jargon for the <details>/<summary> HTML elements and is never spelled out, so an agent must infer the subject from the tool name rather than the description. It draws no distinction from any of the many other bpj_html_* checks.

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?

The description offers no when-to-use context, no prerequisites, and no exclusions or alternatives. It never says to use this over the sibling accessibility/structure checks or under what conditions a details/summary audit is warranted. The agent must derive invocation conditions from the tool name alone.

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.