Skip to main content
Glama
Prettier MCP Formatter

Prettier MCP Formatter

List supported file extensions

supported_extensions

Report which file extensions this formatter can handle, including Python when Black is available and extra extensions from allowlisted Prettier plugins you pass in.

Instructions

Report the file extensions this server can format. Includes Python (.py/.pyi) when Black is available. Pass allowlisted plugin package names to include extensions those Prettier plugins provide.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "supported_extensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pluginsNoAllowlisted npm plugin packages to include in the support report.

Output Schema

NameRequiredDescriptionDefault
pluginsYes
languagesYes
extensionsYes
formattersYes
prettierVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does add real context: Python support is conditional on Black being available, and plugin extensions appear only for allowlisted npm packages. These are conditional behaviors an agent could not derive from the schema. It does not mention permissions or failure modes, but for a read-only report tool that is a minor gap.

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?

Three short sentences with the core purpose front-loaded, followed by the conditional Python detail and then the parameter behavior. Nothing is redundant or padded.

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 tool is simple: one optional parameter and an output schema that already defines the return shape. The description covers the conditional environment dependency and the parameter's effect, which is sufficient for correct invocation; only explicit sibling comparison is missing.

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 the baseline is 3, and the description goes beyond it by stating that plugin entries must be allowlisted npm package names and that their purpose is to widen the reported extension set. That adds intent the schema's terse parameter description does not convey.

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 first sentence states a specific verb and resource ('Report the file extensions this server can format'), which is immediately distinguishable from the siblings format_code and cache_info. It is clear and concrete, though it never names how it differs in scope from those siblings.

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

Usage Guidelines3/5

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

The description explains what passing plugin names accomplishes, which is real usage guidance for the single parameter, but it gives no explicit when-to-use or when-not-to-use framing relative to format_code or cache_info. An agent can infer this is a discovery step before formatting, but that inference is left to the agent.

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

Deploy Server

Other Tools