Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

md_property_contents

Reads the controls on the currently visible Property Editor page using current owner paths, without switching pages or writing settings. Returns numeric UI values that do not establish solver or native vertex ownership.

Instructions

Read controls on the currently visible Property Editor page using current owner paths. No page switching or setting writes; numeric UI values do not establish solver/native vertex ownership.

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

Input Schema

NameRequiredDescriptionDefault
budget_msNo
scene_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description must carry the behavioral burden. It usefully discloses that the tool is read-only and does not switch pages or write settings, and adds a semantic caveat that numeric UI values do not establish solver/native vertex ownership. However, it omits operational details such as how budget_ms affects execution, timeout behavior, or permissions.

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?

The definition is two sentences with no filler and the core action is front-loaded. The second sentence packs in useful constraints and a semantic caveat. Slight jargon such as 'current owner paths' keeps it from being maximally accessible, but it is efficiently structured.

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 two-parameter read tool with no annotations and no output schema, the description is only partially complete. It covers scope and read-only behavior but leaves both parameters undocumented and gives no indication of return shape or how budget_ms influences the read. An agent would have to guess at the required scene_token and the time-budget semantics.

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 for both parameters. It never explains the required scene_token or the budget_ms parameter, including its default of 750. Phrases like 'currently visible' and 'current owner paths' imply scene context but do not define or constrain either parameter.

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?

The description states a specific verb and resource: 'Read controls on the currently visible Property Editor page using current owner paths.' It scopes the operation to the visible page and current owner paths, which helps distinguish it from siblings that may navigate or modify property state. It stops short of naming an explicit alternative tool, so it is clear but not maximally differentiated.

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 clear usage context: read controls on the currently visible page, with explicit exclusions ('No page switching or setting writes'). That tells the agent when not to use it for navigation or mutation. It does not name an alternative tool for those excluded operations, leaving the agent to infer them from sibling names.

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