Skip to main content
Glama

Check a plugin

check_plugin
Read-only

Validate an Agent Plugins 1.0 folder (plugin.json, mcp.json, skills/) for install-blocking errors, skipped warnings, and tips, matching Casama's install checks.

Instructions

Check an Agent Plugins 1.0 folder (plugin.json, mcp.json, skills/) on this computer the way Casama checks it at install: errors (refused), warnings (skipped or ignored) and tips.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "check_plugin"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe plugin folder, absolute or relative to where the server runs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, local operation. The description adds useful behavioral context by explaining that it mirrors install-time checks and distinguishes errors that are refused from warnings that are skipped or ignored, plus tips.

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 a single front-loaded sentence with no wasted wording. It packs the target folder contents, local scope, install-time comparison, and result categories into one efficient statement.

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?

For a simple one-parameter, read-only tool, the description is nearly complete: it explains what is checked and the broad result categories. The only minor gap is that it does not specify the exact return format, though no output schema exists to carry that detail.

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%, so the single path parameter is already fully documented as the plugin folder, absolute or relative. The description reinforces that this is a folder on the local computer but does not add syntax or constraints beyond the schema.

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 states a specific verb and resource: checking an Agent Plugins 1.0 folder containing plugin.json, mcp.json, and skills/. It also scopes the operation to a local folder and describes the check categories, making it clearly distinct from the documentation-oriented sibling tools.

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?

Usage is implied by the description of checking a plugin folder the way Casama checks it at install, but there is no explicit when-to-use or when-not-to-use guidance. Since the sibling tools are unrelated documentation tools, no direct alternative is named or needed.

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