Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

plugin_info

Read-only

Fetches detailed information for a named Kiln plugin, helping agents inspect its attributes and capabilities.

Instructions

Get detailed information about a specific plugin.

        Args:
            name: Plugin name.

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": {
      "name": "<name>"
    },
    "name": "plugin_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPlugin name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / name / description
      Added value: +"Plugin name."
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond that - it does not say what "detailed information" includes, whether an unknown name errors, or whether disabled/uninstalled plugins are resolvable.

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

Conciseness4/5

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

The purpose sentence is front-loaded and short, with no filler. The trailing `Args:` block merely duplicates the input schema and could be removed without loss, which keeps it just short of a 5.

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

Completeness3/5

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

For a single-parameter read tool with full annotation coverage and no output schema, this is minimally sufficient - the agent knows what to pass. It is still thin on what comes back and on error behavior for a nonexistent plugin name, which matters for a lookup-by-identifier tool.

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 description coverage is 100% and the single parameter is already documented as "Plugin name", so the description's `name: Plugin name.` line is a pure restatement with no added meaning such as source, format, or identifier convention. Baseline 3 applies when the schema does all the work.

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 description states a specific verb and resource ("Get detailed information about a specific plugin"), which separates it from bulk-retrieval siblings by the word "specific". It never names `list_plugins`, so the differentiation is implicit rather than explicit, but an agent can still tell it fetches one plugin's details.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no mention of when not to use it, and no reference to the obvious alternative `list_plugins` for enumerating plugins. The only guidance is the implied need to already know a plugin name, which the agent must infer.

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