Skip to main content
Glama

HTML language declarations

bpj_html_document_language
Read-onlyIdempotent

Report the root lang and validate explicit lang declarations using Intl language tag parsing.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 closed-world scope, so safety is covered. The description adds one genuinely new behavioral fact — validity is judged via Intl language tag parsing — but says nothing about what the report contains, whether findings are returned as a list, or how the 6000-character input cap affects behavior.

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 the two actions front-loaded and no filler. It could be tightened slightly ('explicit lang declarations' is loose), but nothing is wasted.

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 single-parameter tool, the core intent is conveyed. With no output schema, however, the description carries the burden of describing the return shape and doesn't — an agent cannot tell whether it gets the root lang value, a list of invalid declarations, or both.

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?

The single parameter has 0% schema description coverage; only a bare title 'Source text' and a maxLength. The description never mentions the input at all, so it does not clarify whether the text is a full HTML document, a fragment, or just a tag snippet — a distinction that matters for a root-lang check.

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?

Names two concrete operations on a specific resource: reporting the root lang attribute and validating explicit lang declarations, with the validation mechanism (Intl language tag parsing) spelled out. This distinguishes it reasonably from siblings like bpj_canonicalize_language_tags, though it never explicitly contrasts with bpj_html_track_language_audit.

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 when-to-use guidance, no prerequisites, and no reference to alternatives. An agent seeing bpj_html_track_language_audit and bpj_canonicalize_language_tags alongside this tool has no stated rule for choosing between them.

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.