Skip to main content
Glama

Autoplay media review

bpj_html_autoplay_inventory
Read-onlyIdempotent

Locate autoplaying media and report muted and controls attribute states.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds value by disclosing the reported fields (muted and controls states), but it never defines what counts as autoplaying media (video? audio? iframe?) or how results are shaped/ordered.

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 zero filler; the detection target comes first and the reported attributes second. Nothing in it is redundant.

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

Completeness4/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 does state what is reported (muted and controls attribute states), which is the key return-value information. It is slightly thin on input expectations and detection scope, but sufficient for a simple one-parameter audit tool.

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?

Only one parameter, and the schema description coverage is 0%, so the description must carry the burden. "Locate autoplaying media" implies the input is HTML source text, which partially compensates for the missing schema description, but no constraints (e.g., the 6000-character limit, whether fragments are OK) are conveyed.

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?

Specific verb and resource: "Locate autoplaying media and report muted and controls attribute states" tells the agent exactly what is detected and what is reported. It is reasonably distinct from sibling review tools (e.g., caption tracks), though it never names an alternative or scoping boundary.

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/when-not-to-use guidance, no prerequisites, and no mention of alternatives among the many sibling HTML review tools. Usage is only implied by the name and the word "Locate".

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.