Skip to main content
Glama

Autocomplete token inventory

bpj_html_autocomplete_tokens
Read-onlyIdempotent

Inventory autocomplete tokens, section names, shipping or billing groups and final purpose tokens.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds no behavioral context beyond that: it doesn't say what the returned inventory looks like (counts, token lists, grouped by element), how invalid or missing autocomplete attributes are handled, or that parsing is limited to a 6000-character text blob.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no filler, and the primary subject (autocomplete tokens) is front-loaded. The problem is under-specification rather than verbosity, so it earns only a middling score for structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must convey what the inventory returns, and it only gestures at categories without describing shape or granularity. It also omits the input format (HTML) and any input constraints, leaving the agent unable to predict either the call or the result.

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?

Schema description coverage is 0% for the single required 'text' parameter; only the title 'Source text' hints at content. The description does not state that this must be HTML source, nor what happens with non-HTML input or with text exceeding the maxLength of 6000. With one undocumented parameter, the description should have compensated but does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'inventory' plus 'autocomplete tokens' gives a recognizable resource, and the enumeration of token sub-parts (section names, shipping/billing groups, purpose tokens) narrows it further. However, the description never says the input is HTML markup, so an agent cannot tell whether this parses HTML, JSX, or raw attribute strings. It also doesn't distinguish itself from siblings like bpj_html_landmark_inventory or bpj_html_accesskey_conflicts beyond the token subject.

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 statement of when to use this tool, when not to, or which sibling to prefer for a related audit. The agent is left to infer usage purely from the token vocabulary in the sentence.

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.