Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

search_manual

Read-only

Search Aseprite's user manual to learn how editor features like tilemaps, onion skinning, or slices work; the first query caches the manual and refreshes it every 30 days.

Instructions

Search Aseprite's user manual: how features work in the editor, such as tilemaps, onion skinning, or slices. The first search downloads the manual from GitHub to your cache, then it refreshes every 30 days.

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_manual"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), so the lower bar applies. The description still earns credit by disclosing a non-obvious operational trait: the first search downloads the manual from GitHub into a cache and it refreshes every 30 days, which explains cold-start latency and offline behavior. It says nothing about result format or paging, but that is secondary here.

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 sentences, front-loaded with the purpose and immediately followed by the caching caveat. Every clause carries information, and the example list is doing real scoping work rather than padding.

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 two-parameter read-only search tool with no output schema, the description plus annotations cover nearly everything an agent needs, including the network/cache behavior. The one meaningful gap is the undocumented 'limit' parameter, which the agent must guess from the schema default alone.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden of explaining parameters and it does not. It gives no hint about 'limit' (result count, default 5) and only loosely implies that 'query' is a free-text search string, adding essentially no meaning beyond the bare schema titles.

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?

Names a specific verb and resource ('Search Aseprite's user manual') and scopes it with concrete examples (tilemaps, onion skinning, slices), which clearly separates it from documentation-search siblings such as search_api_docs. It stops short of explicitly naming the alternative tool, so differentiation is inferable from the domain wording rather than stated.

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?

The description tells the agent what kind of content lives here ('how features work in the editor'), which implicitly indicates when to reach for it. There is no explicit when-not guidance and no named alternative to use for other query types, leaving the routing decision partly to inference.

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