Skip to main content
Glama

Table header associations

bpj_html_table_header_links
Read-onlyIdempotent

Check whether each cell headers token identifies a th in the same source table.

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

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 establish that this is a read-only, idempotent, closed-world check. The description adds the key behavioral scope—tokens must resolve to a th in the same table—but does not state the result shape, how violations are reported, or edge-case handling such as duplicate IDs or whitespace.

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 front-loaded sentence with no filler. It is terse, but every word carries task-specific meaning.

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, single-input audit, the description covers the core check but leaves input format and especially output or return behavior unstated, with no output schema to compensate. Enough to identify the tool, not enough for an agent to know what result to expect.

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 only one parameter, text, with 0% schema description coverage. The description implies the input contains a source table but never explicitly says it is HTML source text, nor does it explain the maxLength or how the parser treats the string.

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 names a concrete verification task: checking cell headers tokens against th elements in the same source table. It is clear enough to distinguish from general table extraction tools, though it does not explicitly contrast with sibling tools such as bpj_sheet_header_body.

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?

It says what is checked but not when an agent should choose this audit, what prerequisite HTML structure is required, or when another table or header tool is more appropriate. No alternatives or exclusions are given.

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.