Skip to main content
Glama

browser-compat-mcp-server

Browsercompat List Reference

browsercompat_list_reference
Read-onlyIdempotent

Enumerate the reference vocabulary this server uses: BCD namespaces, BCD browser ids, browserslist agent ids and their BCD counterparts, Baseline states, web-features groups, and ECMAScript snapshots. Use it to build valid inputs for the other tools and to see which target browsers can be evaluated.

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": {
      "topic": "<topic>"
    },
    "name": "browsercompat_list_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesWhich vocabulary to list: bcd_namespaces for the 12 top-level browser-compat-data namespaces, bcd_browsers for the 17 tracked browsers, browserslist_agents for the 19 browserslist ids mapped to browser-compat-data browsers, baseline_states for the 4 Baseline states, groups for the 105 web-features groups, or snapshots for the 11 ECMAScript snapshots.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
topicNoThe topic that was listed.
entriesNoEvery entry in the requested vocabulary.
attributionNoRequired attribution for the caniuse-derived usage figures in this response.
data_versionNoVintage of each bundled dataset behind this answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / topic / description
      Previous value: -"Which vocabulary to list: bcd_namespaces for the 12 top-level browser-compat-data namespaces, bcd_browsers for the 17 tracked browsers, browserslist_agents for the 19 browserslist ids mapped to browser-compat-data browsers, baseline_states for the 4 Baseline states, groups for the 104 web-features groups, or snapshots for the 11 ECMAScript snapshots."New value: +"Which vocabulary to list: bcd_namespaces for the 12 top-level browser-compat-data namespaces, bcd_browsers for the 17 tracked browsers, browserslist_agents for the 19 browserslist ids mapped to browser-compat-data browsers, baseline_states for the 4 Baseline states, groups for the 105 web-features groups, or snapshots for the 11 ECMAScript snapshots."
  2. Changed1 schema field changed
    • changedOutput schema / properties / entries / items / properties / usage_percent / description
      Previous value: -"Share of tracked global traffic attributed to this browserslist agent."New value: +"Percentage points of global traffic attributed to this browserslist agent."
  3. Changed1 schema field changed
    • changedInput schema / properties / topic / description
      Previous value: -"Which vocabulary to list: bcd_namespaces for the 12 top-level browser-compat-data namespaces, bcd_browsers for the 17 tracked browsers, browserslist_agents for the 19 browserslist ids mapped to browser-compat-data browsers, baseline_states for the 4 Baseline states, groups for the 103 web-features groups, or snapshots for the 11 ECMAScript snapshots."New value: +"Which vocabulary to list: bcd_namespaces for the 12 top-level browser-compat-data namespaces, bcd_browsers for the 17 tracked browsers, browserslist_agents for the 19 browserslist ids mapped to browser-compat-data browsers, baseline_states for the 4 Baseline states, groups for the 104 web-features groups, or snapshots for the 11 ECMAScript snapshots."
  4. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description's main behavioral contribution is framing the content as a fixed reference vocabulary, which largely restates what the annotations imply, and it says nothing about result size or ordering. That is adequate but not rich added context.

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?

Two sentences, front-loaded with the verb and scope, and the second sentence carries the actionable guidance. The six-item list partially duplicates the enum values in the schema, which is mild redundancy but keeps the purpose readable at a glance.

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 one fully documented enum parameter, full annotations, and an output schema covering return values, the definition gives an agent everything needed to call it correctly. The only minor gap is that it does not hint at result size or ordering, which matters for the larger vocabularies (105 groups).

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?

Schema coverage is 100% and the single enum parameter is documented in detail, including item counts for each vocabulary. The description names the same six categories without adding syntax, defaults, or selection heuristics beyond what the schema already states, so the baseline of 3 applies.

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

Purpose5/5

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

"Enumerate the reference vocabulary this server uses" is a specific verb+resource, and the enumeration that follows (BCD namespaces, browser ids, browserslist agents, Baseline states, groups, snapshots) makes the scope concrete. It is clearly distinguishable from the sibling tools, which operate on features rather than on the vocabulary itself.

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

Usage Guidelines4/5

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

"Use it to build valid inputs for the other tools and to see which target browsers can be evaluated" gives a clear when-to-use condition tied to the siblings. It stops short of explicit exclusions (e.g. "do not use to check support — use check_baseline"), so it is a 4 rather than a 5.

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.