Skip to main content
Glama
Sign In
threejs-devtools-mcp

threejs-devtools-mcp

by DmitriyGolub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

find_objects

Read-onlyIdempotent

Search Three.js scene objects by type, material, visibility, name pattern, geometry, child count, or custom property to locate matching nodes for inspection.

Instructions

[INSPECT] Read-only. Search objects by type, material, visibility, name pattern, or custom property.

Input Schema

NameRequiredDescriptionDefault
typeNoObject type: Mesh, Group, InstancedMesh, Light, etc.
limitNoMax results (default: 50, max: 200)
valueNoExpected value of the custom property
visibleNoFilter by visibility
materialNoMaterial name or type
propertyNoCustom property name to check
hasGeometryNoObjects with/without geometry
minChildrenNoMinimum number of children
namePatternNoRegex to match object names

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / hasGeometry / description
      Previous value: -"Filter objects with/without geometry"New value: +"Objects with/without geometry"
    • changedInput schema / properties / material / description
      Previous value: -"Material name or type to filter by"New value: +"Material name or type"
    • changedInput schema / properties / namePattern / description
      Previous value: -"Regex pattern to match object names"New value: +"Regex to match object names"
    • changedInput schema / properties / property / description
      Previous value: -"Custom property name to check on the object"New value: +"Custom property name to check"
    • changedInput schema / properties / value / description
      Previous value: -"Expected value for the custom property"New value: +"Expected value of the custom property"
    • addedInput schema / properties / value / type
      Added value: +[
+  "string",
+  "number",
+  "boolean"
+]
  2. First observedv0.4.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description's 'Read-only' line is largely redundant. It adds no new behavioral context such as result shaping, pagination/limit behavior, or how filters combine. No contradiction with annotations.

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

Conciseness4/5

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

Two compact lines with the category and safety tag front-loaded before the functional sentence. Slight redundancy between the '[INSPECT]' tag and 'Read-only', but no wasted prose.

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

Completeness3/5

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

For a 9-parameter, all-optional filter tool with no output schema, the description is adequate on capabilities but silent on how multiple filters compose (AND/OR), result ordering, and what a match looks like. An agent can call it, but edge behavior is left to guesswork.

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% with all 9 parameters documented, so the schema carries the burden and baseline is 3. The description names a subset of the filter dimensions but adds no syntax, defaults, or combination semantics beyond what the schema already states.

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?

States a specific verb (Search) and resource (objects) plus the filter facets it supports (type, material, visibility, name pattern, custom property). This distinguishes it from singular inspection siblings like object_details, though it never names an alternative explicitly.

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 '[INSPECT] Read-only' tag implies a discovery/read context, and the filter list implies when the tool is useful, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., scene_tree, object_details). Usage is inferable rather than stated.

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