Skip to main content
Glama

HTML direction declarations

bpj_html_text_direction_review
Read-onlyIdempotent

Validate explicit dir values and check that bdo uses a fixed ltr or rtl direction.

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

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 readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so safety is covered. The description contributes the actual rule set being enforced (valid dir values, bdo must be ltr/rtl), which is useful, but it says nothing about reporting behavior — whether all violations are returned, first-only, or whether severity is attached.

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?

One short sentence, front-loaded with the primary check and immediately followed by the secondary bdo constraint. No filler, no restatement of the tool name.

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 single-parameter, read-only validator this is close to adequate, and the annotations plus schema cover most structured needs. However, with no output schema the description should say roughly what comes back (a list of violations? a pass/fail?) and should confirm the input format, both of which are left to inference.

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?

There is a single parameter with 0% schema description coverage; the schema only offers the title "Source text" and a 6000-character cap. The description's mention of dir/bdo implicitly signals that the input is HTML markup, partially compensating, but it never explicitly says the text must be HTML source rather than extracted plain text.

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 uses specific verbs ("Validate", "check") against specific resources ("explicit dir values", "bdo ... fixed ltr or rtl"), which is enough to distinguish this from sibling HTML review tools such as bpj_html_document_language or bpj_html_duplicate_attributes. It stops short of explicitly naming what it is not, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer you run this on HTML source to audit direction declarations. There is no statement of when to prefer it over the other bpj_html_* review tools, no prerequisite (e.g. input must be HTML markup, not plain prose), and no exclusions.

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.