Skip to main content
Glama

check_skill_compatibility

Agent-facing guidance, not user-facing copy. This legacy-named tool provides published Skill information, not MCP compatibility or host-installation verification. Complete normal tasks first; no Skill check, install or update is required for business calls. If installation is unknown, say "if you have not installed the Skill" rather than claiming it is missing. Suggest installation or an available update at most once on first use or when needed; the host tracks reminders per conversation and must not repeat them during retries. Current, ahead or unknown versions must not be called incompatible or forced to downgrade. Use only the returned environment-specific installation_url, never invent a release or endpoint. If MCP is missing, guide connection using a verified official source. If authentication fails, guide the user to protected client settings to enter an API Key; never ask them to paste a key into chat. Keep normal authentication, permissions, rate limits and download safety. Never hide real business failures, missing tools or task limitations such as missing product dimensions. If the user explicitly asks for diagnostics, explain actual facts honestly. Do not replay successful writes during recovery/retries. Install or reload only with host support and user authorization; never claim host-loading success.

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": "check_skill_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
skill_idNoActual Skill top-level name; optional for discovery
skill_versionNoActual installed metadata.version; stable MAJOR.MINOR.PATCH

Output Schema

NameRequiredDescriptionDefault
statusYesNon-blocking published release hint; not a compatibility decision
messageYesmessage; empty when unavailable
traceIdYestraceId; empty when unavailable
skill_idYesskill_id; empty when unavailable
installation_urlYesinstallation_url; empty when unavailable
latest_skill_versionYeslatest_skill_version; empty when unavailable
independent_mcp_availableYesBusiness tools remain subject to normal authentication and permissions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden, and it does disclose real behavior: it returns an environment-specific installation_url, never a fabricated endpoint, and it describes version semantics (current/ahead/unknown must not be called incompatible). But most of the text is agent conversational policy (reminder tracking, retry handling, key handling) rather than properties of this call – e.g. it never says whether an omitted skill_id returns a discovery list versus an error. Helpful but only partly about the tool itself.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the name-correction are front-loaded, which is good, but the body is a dense wall of overlapping prohibitions around retries, reminders, installation and key handling that repeat the same 'do not' shape. Several sentences serve general agent conduct rather than selecting or invoking this tool, so length outpaces informational yield.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is trivial (two optional params) and an output schema exists, so return values need not be explained. Yet the description still leaves the core interaction underspecified: it never states what a call with no arguments yields, what the Skill payload contains, or when exactly the agent should call it (only what not to do around it). It is complete on guardrails and incomplete on the call itself.

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

Parameters3/5

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

Schema coverage is 100% and both parameters already document themselves as optional discovery inputs and a stable MAJOR.MINOR.PATCH version. The description adds semantic constraints on skill_version – do not treat ahead/unknown as incompatible or force a downgrade – which is a genuine addition, but it says nothing about what happens when either parameter is omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says the tool "provides published Skill information" and explicitly disclaims being an MCP compatibility or host-installation check, which usefully corrects the misleading name. However, "published Skill information" is vague – it never says what data comes back (versions? install URLs? metadata?) or what the tool is fundamentally for beyond discovery. The negation does more work than the positive statement.

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?

Gives concrete when-to-use direction: "Complete normal tasks first; no Skill check, install or update is required for business calls" and limits install/update suggestions to once on first use or when needed. It also carves out an explicit "if the user explicitly asks for diagnostics" path. It lacks any named alternative tool for retrieving Skill or product metadata, so routing between siblings is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources