Skip to main content
Glama
Sign In
gimp-mcp

gimp-mcp

by abelduarte
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

gimp.procedure.describe

Get details of a GIMP PDB procedure, including its arguments and return values, to understand how to use it.

Instructions

Describe a PDB procedure's arguments and return values.

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": "gimp.procedure.describe"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must fully convey behavior. It does not disclose whether the tool is read-only, what happens if the procedure name is invalid, whether it requires specific permissions, or any side effects. The name implies a query, but this is not explicit.

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?

Single sentence with no superfluous words. Could be slightly expanded for clarity without losing conciseness, but as is, it is efficient.

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?

Given the simple input (one string parameter) and no output schema, the description provides the basic purpose but lacks details on error handling, output format, or example usage. More context would help the agent understand what information is returned.

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 0%, so the description must compensate. It adds meaning by indicating the 'name' parameter identifies a PDB procedure, but does not explicitly state this or provide further details like format or examples. The tool's purpose helps disambiguate, but more explicit documentation would improve clarity.

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?

Description clearly states verb 'Describe' and resource 'a PDB procedure', specifying that it covers both arguments and return values. This distinguishes it from siblings like gimp.procedure.call (execute) and gimp.procedure.search (find).

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?

No guidance on when to use this tool versus alternatives like gimp.procedure.call or gimp.procedure.search. No mention of prerequisites or scenarios, leaving the agent to infer context.

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