Skip to main content
Glama
shuji-bonji

@shuji-bonji/web-compat-mcp

Search Web Platform Features

compat_search
Read-onlyIdempotent

Search browser compatibility data by keyword to find the correct BCD identifier for web platform features across APIs, CSS, HTML, and JavaScript.

Instructions

Search BCD (Browser Compat Data) features by keyword. Use this to find the correct BCD identifier for compat_check.

Searches across 15,000+ web platform features including APIs, CSS properties, HTML elements, JavaScript built-ins, and more.

Args:

  • query (string): Search keyword (e.g., "push", "grid", "service-worker", "fetch")

  • category (string, optional): Filter by category ("api", "css", "html", "javascript", "svg", etc.)

  • limit (number): Max results (default: 20, max: 100)

  • offset (number): Pagination offset (default: 0)

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

Returns: List of matching feature IDs with standard/experimental/deprecated status.

Examples:

  • "Find Push API features" → query: "push", category: "api"

  • "Find CSS grid features" → query: "grid", category: "css"

  • "Find all service worker APIs" → query: "serviceworker", category: "api"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1-100, default: 20)
queryYesSearch keyword to match against feature identifiers (e.g., "push", "grid", "service-worker")
offsetNoNumber of results to skip for pagination (default: 0)
categoryNoFilter by BCD category (e.g., "api", "css", "html", "javascript")
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
Behavior4/5

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

Annotations indicate read-only, idempotent, non-destructive. Description adds that it searches 15k+ features and returns status flags, plus pagination details.

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?

Well-organized: purpose first, then args, examples. Each sentence serves a purpose, no fluff.

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?

Covers all 5 parameters, return type with status, pagination, and examples. No output schema but description adequately explains results.

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?

Schema coverage is 100%. Description reinforces each parameter with examples and context, adding value beyond schema descriptions.

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?

Clearly states it searches BCD features by keyword to find identifiers for compat_check. Differentiates from sibling tools like compat_check by specifying its role in finding identifiers.

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?

Explicitly states when to use (find BCD identifier for compat_check). Does not list exclusions but context implies it's for searching, not checking support.

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