Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

canvas_runtime_capabilities

Inspect trusted native configuration and loaded Qt module identity without loading the bridge to verify available runtime capabilities safely.

Instructions

Inspect trusted native configuration and loaded Qt module identity; never loads the bridge.

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": "canvas_runtime_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 does disclose one important trait — that the bridge is never loaded, i.e. no side effects — but it says nothing about whether the call is read-only in a broader sense, what permissions or trust assumptions apply, or what the inspection actually returns.

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 compact sentence with the action front-loaded and the safety guarantee appended; nothing is redundant. It is arguably too terse for a tool with no output schema, but no sentence fails to earn its place.

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?

With no parameters, no annotations, and no output schema, the description is the only source of information, and it leaves the return shape and the meaning of "trusted native configuration" undefined. It is adequate to know roughly what the tool does, but not enough to predict what an agent will get back.

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 there is no parameter meaning to convey and the baseline of 4 applies. The description correctly does not waste words on arguments.

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 ("Inspect") and a specific resource ("trusted native configuration and loaded Qt module identity"), which is more than a restatement of the name. It does not explicitly distinguish itself from the sibling capability inspectors (curve_runtime_capabilities, cut_qt_runtime_capabilities, scene_adapter_runtime_capabilities), so an agent must infer the canvas scope from the tool name alone.

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 clause "never loads the bridge" implicitly tells the agent this is the safe, side-effect-free way to inspect state, which is a usable selection hint. However, there is no explicit when-to-use statement, no mention of when a sibling capability tool would be preferred, and no stated prerequisites.

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