Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

search_api_docs

Read-only

Search Aseprite's Lua scripting API reference to find classes, methods, and properties before writing run_lua code, so you can use the correct API calls.

Instructions

Search Aseprite's Lua scripting API reference, bundled with this server. Use it before writing run_lua code, for a class, method, or property such as Image:drawImage or selection bounds.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds useful context that the reference is bundled with the server and is Lua-API-specific, but says nothing about result shape, ranking, or how the limit parameter affects output.

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?

Two tightly written sentences with no filler; the core identity is front-loaded and the usage hint follows immediately.

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 two-parameter read-only lookup with no output schema, the description covers identity, timing, and query phrasing. Only the meaning and effect of limit is left undocumented.

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 0% for two parameters. The description compensates for query by showing accepted query forms (class:method, property phrases), but the limit parameter is never explained, so half the schema remains semantically bare.

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?

States a specific verb and resource — searching the bundled Aseprite Lua scripting API reference — and scopes the content type (classes, methods, properties) so it is distinguishable from a general manual lookup or from executing code via run_lua.

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 an explicit trigger: use it before writing run_lua code, and clarifies the query subject with concrete examples like Image:drawImage and selection bounds. It does not address when not to use it or name a sibling alternative such as search_manual, so it stops short of full routing guidance.

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