Skip to main content
Glama
Sign In

pmndrs docs

by io.github.pmndrs
OverviewDiscussionsAdmin

Search Docs

search_docs
Read-onlyIdempotent

Search the current documentation of react-three-fiber, drei, zustand, a11y, react-postprocessing, docs, react-three-jolt, sky, denoiser, design-system. Call this FIRST, before answering any question about one of these libraries: these docs track their current releases, which are newer than your training data, and their APIs changed across major versions (react-three-fiber v9, drei v10, zustand v5 each broke things), so an answer from memory is likely stale. Returns the 10 best-matching pages, best first, each with the lib and path to pass to get_page_content.

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

Input Schema

NameRequiredDescriptionDefault
libNoSearch this library only. Leave out to search all of them.
queryYesWhat to look for: a component, hook, prop or concept, in a few words (e.g. "useFrame", "instanced mesh", "persist middleware"). Every term has to match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changed
    • changedInput schema / properties / lib / enum
      Previous value: -[
-  "react-three-fiber",
-  "drei",
-  "zustand",
-  "a11y",
-  "react-postprocessing",
-  "docs",
-  "react-three-jolt",
-  "sky",
-  "denoiser"
-]New value: +[
+  "react-three-fiber",
+  "drei",
+  "zustand",
+  "a11y",
+  "react-postprocessing",
+  "docs",
+  "react-three-jolt",
+  "sky",
+  "denoiser",
+  "design-system"
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds non-annotation behavior: it returns exactly 10 best-matching pages ranked best-first, each with a lib and path. It does not mention rate limits or auth, but for a read-only search that is a minor omission.

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?

The critical instruction (call this first) and the staleness rationale are front-loaded in one dense sentence, followed by the return shape. No filler sentences; every clause carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description supplies the missing return contract (10 results, ranked, with lib + path). Combined with the annotations covering safety, nothing an agent needs to invoke and consume this tool is 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?

Schema description coverage is 100%, so the schema already documents both the lib enum and the query field, including the AND-match rule. The description adds no extra syntax or format guidance for the parameters, 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) plus the exact resource scope (current docs for ten named libraries), which immediately separates it from get_page_content and get_example. An agent can identify the tool's domain without reading the 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?

Explicitly says to call this FIRST before answering any question about these libraries, and gives the reason (docs track current releases newer than training data, APIs broke across major versions). It also names the downstream sibling: results carry a lib and path to pass to get_page_content.

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

All pmndrs docs toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources