Skip to main content
Glama
shuji-bonji

@shuji-bonji/web-compat-mcp

Check Browser Compatibility

compat_check
Read-onlyIdempotent

Check browser compatibility for a web platform feature with version support across browsers, Baseline status, and links to MDN and spec documentation.

Instructions

Check browser compatibility for a specific web platform feature using MDN Browser Compat Data (BCD).

Returns version support across browsers, Baseline status, and links to MDN/spec documentation.

Args:

  • feature (string): BCD identifier in dot notation (e.g., "api.PushManager", "css.properties.grid", "javascript.builtins.Promise")

  • browsers (string[], optional): Filter to specific browsers (e.g., ["chrome", "safari"]). Defaults to desktop browsers.

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Browser support versions, Baseline status, standard/experimental/deprecated flags, and MDN/spec links.

Examples:

  • "Is Push API supported in Safari?" → feature: "api.PushManager"

  • "Can I use CSS grid?" → feature: "css.properties.grid"

  • "Is Array.at() widely available?" → feature: "javascript.builtins.Array.at"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
featureYesBCD feature identifier using dot notation (e.g., "api.PushManager", "css.properties.grid", "javascript.builtins.Array.at")
browsersNoFilter to specific browsers (e.g., ["chrome", "safari", "firefox"]). Omit for default desktop browsers.
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
Behavior5/5

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

Annotations already indicate read-only and idempotent. The description adds comprehensive behavioral details: returns version support across browsers, Baseline status, flags (standard/experimental/deprecated), and links to MDN/spec documentation. This fully informs the agent of what the tool does beyond safety.

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?

The description is concise and well-structured: a one-sentence purpose, followed by bullet-style Args/Returns, and clear examples. Every sentence adds value without redundancy.

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?

The description covers input, output, and examples adequately. While error handling or edge cases (e.g., invalid feature identifier) are not mentioned, the examples and parameter descriptions provide sufficient guidance for normal use. Annotations cover safety, so no gaps there.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 100% coverage with good descriptions. The description adds value with examples of BCD identifiers, default browsers behavior, and output format options, helping the agent understand parameter usage in context.

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 clearly states the tool checks browser compatibility for a specific web platform feature using BCD, with details on input and output. However, it does not explicitly differentiate from sibling tools like compat_check_support, which might offer a simpler query for the same feature.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., compat_check_support for quick yes/no, compat_compare for comparing features). The sibling list is available context, but the description does not reference them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shuji-bonji/web-compat-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server