README documents a `get_available_features` tool that the server does not expose

README.md line 316 documents a tool named get_available_features:

• get_available_features: Get a list of available Vuetify features, including components, directives, and composables.

There are two problems with that line.

1. The tool name does not exist

A tools/list call against the hosted server (https://mcp.vuetifyjs.com/mcp, serverInfo reports Vuetify MCP 0.11.0) returns 25 tools, and get_available_features is not among them. The closest match — and, judging by the description, the tool actually meant — is get_feature_guides.

An agent that trusts the README calls a name that does not resolve:

MCP error -32602: Tool get_available_features not found

2. The description does not match what the real tool returns

get_feature_guides returns 12 framework documentation topics, with no components, directives or composables among them:

accessibility, aliasing, application-layout, blueprints, dates, display-and-platform,
global-configuration, icon-fonts, internationalization, programmatic-scrolling,
sass-variables, theme

So "including components, directives, and composables" describes something the tool does not do. This is the more costly half, because it advertises a capability the server does not have. Every tool in the server needs the component name up front (get_component_api_by_version answers "not found" without it), so there is in fact no way to ask "which component does X?" — but the README implies there is, which sends agents looking for a discovery path that isn't there.

Notably, the server's own description of the tool is already correct ("Get a list of available features in the documentation."); only the README's is wrong.

Reproduction

curl -sS -X POST https://mcp.vuetifyjs.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Grep the result for get_available_features (absent) and get_feature_guides (present), then call get_feature_guides and compare its output with the README's description.

Expected

The README lists tools the server actually exposes, described by what they actually return.

Suggested fix

Rename the entry to get_feature_guides and reword it, e.g. "Get a list of Vuetify framework feature guides (theme, i18n, accessibility, SASS variables, …)."

Environment

• Hosted server https://mcp.vuetifyjs.com/mcp, serverInfo Vuetify MCP 0.11.0
• README as of master, line 316
• Verified 2026-08-29

Minor, possibly separate

get_feature_guides prefixes its output with "Available Vuetify 3 features:" while Vuetify 4 is current. Might be intentional if the guide set is genuinely v3-era, but worth a glance.

Start with the tool list in README.md around line 316 and compare its entries with the reproduction commands in the issue. Confirm the hosted server exposes get_feature_guides and review that tool's returned topics before updating the name and description. Done means the README names an exposed tool and accurately describes its output.