Skip to main content
Glama
shuji-bonji

@shuji-bonji/web-compat-mcp

List Features by Baseline Status

compat_list_baseline
Read-onlyIdempotent

Filter and list web platform features by their Baseline status: Widely Available, Newly Available, or not yet Baseline. Supports filtering by feature group and pagination.

Instructions

List web platform features filtered by their Baseline status.

Use this to discover which features are Widely Available, Newly Available, or not yet Baseline.

Args:

  • status (string, optional): Filter by "high" (Widely Available), "low" (Newly Available), or "false" (Not Baseline)

  • group (string, optional): Filter by feature group (e.g., "css", "javascript", "forms")

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

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

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

Returns: Paginated list of features with their Baseline status and availability dates.

Examples:

  • "List all Widely Available features" → status: "high"

  • "What CSS features are Newly Available?" → status: "low", group: "css"

  • "What features aren't Baseline yet?" → status: "false"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupNoFilter by web-features group (e.g., "css", "javascript", "forms")
limitNoMaximum number of results to return (1-100, default: 20)
offsetNoNumber of results to skip for pagination (default: 0)
statusNoFilter by Baseline status: "high" (Widely Available), "low" (Newly Available), "false" (Not Baseline)
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 already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral context such as pagination defaults (limit, offset) and output format options (markdown/json), which are beyond what annotations provide. No contradictions.

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 well-structured with clear sections (list function, Args, Returns, Examples). It is concise, with no fluff, and every sentence provides necessary information. The examples are particularly helpful for quick understanding.

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?

Given the tool has 5 parameters, no output schema, and a clear purpose, the description covers all necessary aspects: parameters, defaults, return structure (paginated list with status and dates), and examples. It could mention that results are sorted or other details but is sufficient for an agent.

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%, so baseline is 3. The description adds meaning by explaining each parameter's purpose, enumerating values for status and response_format, and specifying defaults and constraints (e.g., limit range, offset behavior). This goes beyond the 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?

The description clearly states the tool lists web platform features filtered by Baseline status, using specific verbs and resource. It distinguishes from sibling tools like compat_check and compat_search by focusing on listing and filtering by status.

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?

The description provides explicit context for when to use the tool (discover features by Baseline status) and includes multiple examples covering different use cases. However, it does not explicitly mention when not to use it or provide direct alternatives among sibling tools, though the use case is clear enough.

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