Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

scene_adapter_runtime_capabilities

Read trusted scene adapter runtime configuration and capabilities without loading native code, so AI clients can inspect available options before editing or verifying scenes.

Instructions

Read trusted configuration state without loading native code.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scene_adapter_runtime_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does disclose two meaningful traits — the operation is a read, and it occurs "without loading native code" (a genuine side-effect guarantee that distinguishes it from probe/drag siblings). It says nothing, however, about what state is returned, caching, or failure modes.

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?

A single sentence, front-loaded with the verb, with no wasted clauses. Slightly penalized because "trusted" is doing vague work rather than specifying the state being read.

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?

There is no output schema and no annotations, so the description is the only source of information about what the tool returns — yet it never says what "configuration state" or capabilities actually consist of. For a capabilities-listing tool this is a significant gap; an agent knows it is safe to call but not what it will learn.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema is complete by definition and the description has nothing parameter-related to compensate for. The baseline of 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read trusted configuration state" names a verb and a resource, but the resource is abstract — it never says the tool returns the scene adapter's runtime capabilities, and it does nothing to distinguish this tool from the many sibling *_runtime_capabilities and *_probe_runtime tools. The purpose is inferable from the name but not sharpened by the description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of alternatives (canvas_runtime_capabilities, curve_runtime_capabilities, cut_qt_runtime_capabilities, md_capabilities), and no prerequisites. The agent must infer the context entirely from the name.

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