Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_adapter_select_pattern

Selects a fresh UUID via SDK and verifies index getters and exact unique name, letting you confirm the correct pattern before inspecting the current 3D view.

Instructions

Select one fresh UUID using SDK SelectPatternViaIndex(index, keepPreviousSelection=False), then verify all index getters and exact unique name. Selection only, no geometry/OS input. This bool does not choose 3D. Inspect current 3D view after selection before a pixel-based primitive.

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": {
      "pattern_uuid": "<pattern_uuid>",
      "scene_token": "<scene_token>"
    },
    "name": "world_adapter_select_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idNo
scene_tokenYes
pattern_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that keepPreviousSelection=False (existing selection is cleared) and that verification of index getters/name occurs, but says nothing about error behavior when the UUID is stale, permission/auth needs, or what the call returns. The sentence 'This bool does not choose 3D' references a boolean that does not exist in the schema, muddying rather than clarifying behavior.

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?

Front-loaded with the action, but the four sentences are jargon-dense ('fresh UUID', 'verify all index getters', 'exact unique name') and include an unexplained reference to a boolean that is not in the schema, which costs more clarity than the terseness buys.

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

Completeness2/5

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

For a 3-parameter tool with no annotations, no output schema and 0% schema coverage, the description is too thin: it neither maps parameters to inputs nor explains return/verification results. The implicit selection-clearing side effect and the SDK-internal terminology need far more grounding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 compensate and largely fails. It references an 'index' argument inside SelectPatternViaIndex, but the schema exposes pattern_uuid, scene_token and request_id with no explanation of any of them — the naming mismatch actively risks an agent guessing at parameter meaning.

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 and resource ('Select one fresh UUID' of a pattern) and names the underlying SDK call plus the post-selection verification step. Scope is bounded ('Selection only, no geometry/OS input'), which distinguishes it from transform/drag siblings, but it never contrasts itself with the sibling md_select_pattern, so an agent cannot tell which of the two selection tools to prefer.

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?

Gives a downstream workflow hint ('Inspect current 3D view after selection before a pixel-based primitive') and an explicit out-of-scope statement. However there is no when-to-use vs when-not-to-use routing, no prerequisites, and no indication of when re-selection is required.

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