Skip to main content
Glama

Drawcall

by io.github.drawcall-ai
OverviewDiscussionsAdmin

Search Drawcall guides and APIs

search_skills
Read-onlyIdempotent

Search Drawcall workflows and APIs for apps, games and assets. Discover asset sourcing as well as runtime libraries. Source visual content from @drawcall/market first. When its candidates do not fit, consult @drawcall/generate for generation options and prerequisites before settling on a fallback. Reserve hand-authored geometry for gameplay structure or explicitly procedural content. @drawcall/rig adds skeletons and skin weights when needed. This searches documentation, not Market inventory: read the guides to find and inspect actual assets. Search covers all supported packages automatically, including in an empty project. Returns up to five paths with excerpts; read_skills provides the full workflows and APIs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesWhat you want to implement or learn how to do

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYesThe five best, best first, at most one per document
packagesYesEvery selected package, in selection order

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed4 schema fields changed
    • removedInput schema / properties / packages
      Removed value: -{
-  "items": {
-    "description": "An npm package as name@version (the installed version), or a bare name for its latest",
-    "type": "string"
-  },
-  "maxItems": 200,
-  "minItems": 1,
-  "type": "array"
-}
    • changedInput schema / properties / query / description
      Previous value: -"One concrete question, goal or symptom"New value: +"What you want to implement or learn how to do"
    • changedInput schema / required
      Previous value: -[
-  "query",
-  "packages"
-]New value: +[
+  "query"
+]
    • changedOutput schema / properties / packages / description
      Previous value: -"Every requested package, in request order"New value: +"Every selected package, in selection order"
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/no-destructive, so the safety profile is covered. The description goes beyond them by disclosing that the search spans all supported packages automatically (even in an empty project) and returns up to five paths with excerpts, which is meaningful behavioral context.

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

Conciseness3/5

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

Purpose and the key constraint ('searches documentation, not Market inventory') are front-loaded, but eight sentences for a single-parameter search tool includes some padding and restatement. The mid-section asset-sourcing advice is useful routing but makes the block longer than needed.

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?

An output schema exists, so return values need not be fully explained, yet the description still notes the five-path excerpt limit and directs the agent to read_skills for full content. Scope, sibling routing, and result characteristics are all covered; only minor details like exact matching behavior are absent.

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?

There is only one parameter and schema description coverage is 100%, with the schema already explaining the query field as 'What you want to implement or learn how to do'. The description adds no syntax, format, or scoping constraints beyond that, so the baseline 3 applies.

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 (Search) and resource (Drawcall workflows and APIs), plus the domain (apps, games, assets). It explicitly distinguishes itself from the sibling read_skills ('read_skills provides the full workflows and APIs') and clarifies it searches documentation, not Market inventory, so an agent can select it without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit routing rules: source visual content from @drawcall/market first, fall back to @drawcall/generate when candidates don't fit, reserve hand-authored geometry for gameplay structure, and use @drawcall/rig for skeletons/skin weights. It also names the escalation path to read_skills for full workflows, leaving nothing to inference.

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

All Drawcall toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources