Skip to main content
Glama

Search the Casama gallery

gallery_search
Read-only

Search the Casama gallery (gallery.casama.ai) for ready-made skills, apps, routines, bots, plugins, starter sets and looks before writing a new one. Returns the best matches with what each can access, what it needs and its page. Add one in Casama from its page, or start from it with casama init --from-gallery bot/<id> or plugin/<id>.

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": "gallery_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
typesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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=false), and the description adds useful context beyond them: the shape of results ('what each can access, what it needs and its page') and how to act on a hit. It does not mention ordering, empty-result behavior, or rate limits, but for a read-only search that is a minor gap.

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?

Three sentences, front-loaded with what and where, then what comes back, then what to do with a match. Every clause carries information; nothing is redundant or padded.

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?

No output schema exists, but the description compensates by summarizing the returned fields and the follow-up invocation paths. The main remaining hole is the undocumented `limit` and the filter semantics of `types` for a three-parameter 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 0%, so the description must carry the burden. It partly does: the enumerated content kinds ('skills, apps, routines, bots, plugins, starter sets and looks') loosely map to the `types` enum values, but it never says `types` filters results, never explains `limit`, and never clarifies the `query` syntax.

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 ('Search the Casama gallery') plus the concrete domain (gallery.casama.ai) and the content classes it covers. The doc-oriented siblings (search_docs, read_doc) are clearly different, so an agent can disambiguate without opening a schema.

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?

Explicitly gives the trigger condition - search the gallery 'before writing a new one' - and then describes the two follow-up paths (add from its page, or `casama init --from-gallery bot/<id>`). No explicit exclusion against the doc-search siblings, which keeps it from a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.