Skip to main content
Glama

browser-compat-mcp-server

Browsercompat Search Features

browsercompat_search_features
Read-onlyIdempotent

Find web features by plain name or keyword when the canonical key is unknown, across CSS, JavaScript, HTML, Web APIs, SVG, MathML, WebAssembly, and HTTP headers. Returns ranked matches with the BCD key, the web-features id, the Baseline state, a one-line support summary, and which field matched. Feed a result key into browsercompat_get_feature for the full record.

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": {
      "query": "<query>"
    },
    "name": "browsercompat_search_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNoRestrict results to features in one web-features group or any group nested under it, for example "selectors" or "css". Keys with no web-features mapping never match. Call browsercompat_list_reference with topic groups for valid ids.
limitNoResults to return on this page, 1 to 1000; the page holds that many, fewer only once the matches run out. When matches remain past this page, nextOffset continues.
queryYesPlain-language name, keyword, or code notation, for example "container query", "fromAsync", "Array.prototype.at", "display: grid", or "<dialog>".
offsetNoNumber of ranked matches to skip before returning results, for paging past limit. Pass the nextOffset from the previous response.
baselineNoRestrict results to one Baseline state.
snapshotNoRestrict results to features in one ECMAScript snapshot, for example "ecmascript-2023". Call browsercompat_list_reference with topic snapshots for valid ids.
namespaceNoRestrict results to one top-level browser-compat-data namespace.

Output Schema

NameRequiredDescriptionDefault
capNoThe page size requested in limit.
errorNoPresent when the call failed. Absent on success.
shownNoNumber of results on this page.
resultsNoRanked matches, best first. An empty array is a successful search with no hits.
truncatedNoTrue when more matches remain past this page.
nextOffsetNoThe offset of the next page. Present only while matches remain past this page.
totalCountNoMatches across every page, before offset and limit apply.
data_versionNoVintage of each bundled dataset behind this answer.
offsetNoticeNoWhy a page came back empty although the search matched.
noMatchNoticeNoHow to broaden a search that matched nothing.
appliedFiltersNoFilters the server applied to this search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results to return, at most 50 per call; a value from 51 to 1000 is served as 50. When matches remain, cap reports the size applied and nextOffset continues."New value: +"Results to return on this page, 1 to 1000; the page holds that many, fewer only once the matches run out. When matches remain past this page, nextOffset continues."
    • changedOutput schema / properties / cap / description
      Previous value: -"The page size applied: limit, or 50 when limit was above 50."New value: +"The page size requested in limit."
  2. Changed1 schema field changed
    • changedOutput schema / properties / results / items / properties / support_summary / description
      Previous value: -"One line over the Baseline core browsers, with — for unsupported and ? for unknown."New value: +"One line over the Baseline core browsers: addition release with ≤ for an upper bound and (partial), (prefixed), or (flagged) for qualified support; — for unsupported, removed, or preview-only; ? for unknown."
  3. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results to return, from 1 to 50."New value: +"Maximum results to return, at most 50 per call; a value from 51 to 1000 is served as 50. When matches remain, cap reports the size applied and nextOffset continues."
    • changedInput schema / properties / limit / maximum
      Previous value: -50New value: +1000
    • changedOutput schema / properties / cap / description
      Previous value: -"The limit that was applied."New value: +"The page size applied: limit, or 50 when limit was above 50."
  4. Changed15 schema fields changed
    • addedInput schema / properties / group
      Added value: +{
      +  "description": "Restrict results to features in one web-features group or any group nested under it, for example \"selectors\" or \"css\". Keys with no web-features mapping never match. Call browsercompat_list_reference with topic groups for valid ids.",
      +  "maxLength": 100,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Number of ranked matches to skip before returning results, for paging past limit. Pass the nextOffset from the previous response.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Plain-language name or keyword, for example \"container query\" or \"fromAsync\"."New value: +"Plain-language name, keyword, or code notation, for example \"container query\", \"fromAsync\", \"Array.prototype.at\", \"display: grid\", or \"<dialog>\"."
    • addedInput schema / properties / snapshot
      Added value: +{
      +  "description": "Restrict results to features in one ECMAScript snapshot, for example \"ecmascript-2023\". Call browsercompat_list_reference with topic snapshots for valid ids.",
      +  "maxLength": 100,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedOutput schema / properties / appliedFilters / properties / group
      Added value: +{
      +  "description": "web-features group filter the search applied, nested groups included.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / appliedFilters / properties / snapshot
      Added value: +{
      +  "description": "ECMAScript snapshot filter the search applied.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_query`: query is whitespace-only after normalization, or normalizes to zero tokens. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_query`: query is whitespace-only after normalization, or normalizes to zero tokens. `unknown_group`: group names no web-features group in the bundled data. `unknown_snapshot`: snapshot names no ECMAScript snapshot in the bundled data. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "invalid_query"
      -]New value: +[
      +  "invalid_query",
      +  "unknown_group",
      +  "unknown_snapshot"
      +]
    • addedOutput schema / properties / nextOffset
      Added value: +{
      +  "description": "The offset of the next page. Present only while matches remain past this page.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / offsetNotice
      Added value: +{
      +  "description": "Why a page came back empty although the search matched.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / results / items / properties / matched_on / description
      Previous value: -"Which field matched the query, so the ranking can be inspected."New value: +"Which field matched the query, so the ranking can be inspected. path_suffix means the key ends in the dotted or property-value notation the query used, such as Element.animate or display: grid."
    • changedOutput schema / properties / results / items / properties / matched_on / enum
      Previous value: -[
      -  "bcd_key",
      -  "baseline_id",
      -  "name",
      -  "caniuse_title",
      -  "path_segment",
      -  "description",
      -  "path_tokens"
      -]New value: +[
      +  "bcd_key",
      +  "baseline_id",
      +  "name",
      +  "caniuse_title",
      +  "path_suffix",
      +  "path_segment",
      +  "description",
      +  "path_tokens"
      +]
    • changedOutput schema / properties / shown / description
      Previous value: -"Number of results returned."New value: +"Number of results on this page."
    • changedOutput schema / properties / totalCount / description
      Previous value: -"Matches before the display cap was applied."New value: +"Matches across every page, before offset and limit apply."
    • changedOutput schema / properties / truncated / description
      Previous value: -"True when matches exceeded limit."New value: +"True when more matches remain past this page."
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered; the description adds genuinely new behavioral context by saying matches are ranked and listing what a result carries (BCD key, web-features id, Baseline state, one-line support summary, matched field). It does not discuss pagination behavior in prose, but the offset/limit parameters already document nextOffset paging.

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?

Two sentences, front-loaded with the purpose and condition before the return-shape and next-step information. Every clause carries distinct information: what it searches, over what scope, what comes back, and where to go next.

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

Completeness5/5

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

With a full output schema, complete parameter documentation, and read-only/idempotent annotations, the description only needs to supply purpose, selection condition, and workflow continuity — and it does all three. Nothing an agent needs in order to call this correctly or interpret the result appears to be missing.

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 description coverage is 100%, with every parameter (including enum-constrained namespace and baseline, and group/snapshot guidance pointing at browsercompat_list_reference) documented inline. The description adds only the general 'plain name or keyword' framing and does not explain filtering or paging semantics beyond the schema, so baseline 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?

States a specific verb and resource ('Find web features by plain name or keyword') plus the scope (CSS, JavaScript, HTML, Web APIs, SVG, MathML, WebAssembly, HTTP headers) and the enabling condition ('when the canonical key is unknown'). It also names the sibling it complements (browsercompat_get_feature), so an agent can distinguish a fuzzy search from a key lookup without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit selection condition ('when the canonical key is unknown') and an explicit follow-up route ('Feed a result key into browsercompat_get_feature for the full record'), which together tell the agent when this tool is the right entry point versus the record-fetch sibling. No exclusions or rate caveats are stated, but none are needed for a read-only search.

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.