Skip to main content
Glama

HTML landmark inventory

bpj_html_landmark_inventory
Read-onlyIdempotent

List semantic landmark candidates and explicit landmark roles with any supplied labels.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that results include both implicit candidates and explicit roles plus labels, which is useful, but it says nothing about the input's size limit, how implicit candidates are detected, or what the output entries look like.

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 compact sentence with no filler, front-loading the resource being listed. It is appropriately sized for a simple read-only inventory tool, though the phrase 'with any supplied labels' is slightly compressed and could be clearer.

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 no output schema, the description bears responsibility for describing return values; it names the fields loosely (candidates, roles, labels) but not their structure or granularity. For a single-input read-only tool this is close, but a brief note on result shape and input expectations would make it complete.

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 schema has a single required 'text' parameter with zero description coverage, and the prose never mentions it — nor does it clarify that this is HTML source rather than a URL or file path. The schema title 'Source text' and the 6000-character cap partially fill the gap, leaving this adequate but underspecified.

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 gives a specific verb ('List') and a precise resource ('semantic landmark candidates and explicit landmark roles with any supplied labels'), which distinguishes it from the count-oriented sibling bpj_html_main_landmark_count. It clearly outlines what is enumerated, though it never explicitly contrasts itself with that sibling.

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 guidance on when to use this tool versus the main-landmark count or the other HTML audit tools, and no prerequisites or exclusions are stated. Usage is only implied by the tool name and the word 'List'.

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.