Skip to main content
Glama

Main landmark count

bpj_html_main_landmark_count
Read-onlyIdempotent

Count main elements or main roles without a directly applied hidden or aria-hidden attribute.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real behavioral context by disclosing the exclusion rule (elements/roles with a directly applied hidden or aria-hidden attribute are skipped), which is exactly the kind of counting-semantics detail annotations cannot convey. It does not say what the output looks like or how multiple matches are reported, which keeps it at a 3.

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?

A single sentence that leads with the action and resource, then attaches the qualifying rule. Nothing is redundant or padded.

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 simple read-only counting tool with no output schema, the definition covers the counting rule competently and annotations cover safety. What is missing is any characterization of the input text parameter and the shape of the returned count, which leaves a gap for a tool that has exactly one required input.

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 one required parameter with 0% schema description coverage, so the description carries the full burden, yet it never mentions the input at all. The agent cannot tell from the definition whether 'text' is raw HTML source, a fragment, or something else, nor what the 6000-character limit implies.

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 (count) and a precise resource (main elements or role=main), plus the exclusion rule for hidden/aria-hidden. It is clear on its own, though it never distinguishes itself from the sibling bpj_html_landmark_inventory, which sounds like it covers overlapping ground.

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?

No guidance on when to use this versus the landmark inventory or any other counting tool, and no prerequisites or input expectations are stated. The agent must infer usage purely from the name and the one-sentence scope.

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.