Skip to main content
Glama
Sign In

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

NameRequiredDescriptionDefault
queryYesWhat you want to implement or learn how to do

Output Schema

NameRequiredDescriptionDefault
resultsYesThe five best, best first, at most one per document. Empty until every selected package is ready.
packagesYesEvery selected package, in selection order

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / results / items / properties / uses / description
      Previous value: -"For a returned section: paths of declaration sources it uses"New value: +"Declaration source paths relevant to the matched guide passage"
  2. Changed1 schema field changed
    • changedOutput schema / properties / results / items / properties / excerpt / description
      Previous value: -"The first lines: of a section its text, of a type its declaration"New value: +"Relevant guide text or a declaration from the public API and its supporting types"
  3. Changed4 schema fields changed
    • changedOutput schema / properties / packages / items / properties / status / description
      Previous value: -"ready: searched. indexing: not searched yet, search again shortly. failed: could not be indexed (see error). not_allowed: this service does not index the package."New value: +"ready: indexed and available. indexing: not indexed yet, search again shortly. failed: could not be indexed (see error). not_allowed: this service does not index the package."
    • changedOutput schema / properties / results / description
      Previous value: -"The five best, best first, at most one per document"New value: +"The five best, best first, at most one per document. Empty until every selected package is ready."
    • changedOutput schema / properties / results / items / properties / path / description
      Previous value: -"Where the full text is: a path of the tree, e.g. /@drawcall/physics@0.1.0/types/RigidBody"New value: +"Where the full text is: a path of the tree returned by this service"
    • changedOutput schema / properties / results / items / properties / uses / description
      Previous value: -"For a section: paths of the types it uses"New value: +"For a returned section: paths of declaration sources it uses"
  4. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  5. 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"
  6. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), yet the description still adds real context: it searches documentation rather than inventory, covers all supported packages even in an empty project, and caps results at five paths with excerpts. Return value detail is partly carried by the output schema, so 4 rather than 5.

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?

The core purpose is front-loaded, but the middle is padded with package-routing advice (the @drawcall/rig sentence in particular feels tangential to how to invoke this search). Several sentences are dense and could be trimmed without losing selection-relevant information.

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?

With a rich output schema and strong annotations, the main missing piece is understanding scope, which the description covers (all packages, empty projects, docs vs inventory, result cap). An agent has enough to call it correctly; only the query-phrasing nuance is left implicit.

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 a single parameter with 100% schema description coverage, which already defines the query as 'What you want to implement or learn how to do.' The description adds no syntax, format, or phrasing guidance beyond that, so 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?

The description opens with a specific verb and resource ('Search Drawcall workflows and APIs') and clarifies the domain (apps, games, assets; documentation not Market inventory). It also distinguishes itself from the sibling read_skills by explaining that search returns paths and excerpts while read_skills returns full workflows.

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?

It gives explicit routing guidance among the @drawcall packages (market first, then generate, reserve hand-authored geometry, rig when needed) and states the escalation path to read_skills for full content. What it does not do is spell out a when-not-to-use-this-tool exclusion, so it stops short of a 5.

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