Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

cut_probe_runtime

Probe runtime SDK symbol signatures to confirm whether native Cut support is actually available, because symbol presence alone does not prove the feature works.

Instructions

Read actual SDK symbol signatures only. Presence never proves native Cut works.

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

Input Schema

NameRequiredDescriptionDefault
scene_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does add one genuinely useful disclosure — that observed symbol presence is not proof of working native functionality — but leaves out whether the call is purely read-only, whether it has side effects, permission or auth requirements, and how failures are surfaced.

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 short sentences, front-loaded with the action and followed by the caveat, with no filler. It is efficient, though the brevity contributes to the missing scope and parameter detail rather than reflecting deliberate compression.

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 probe tool with no output schema and no annotations, the description should explain at least the shape or meaning of what is returned and how to act on it. Instead it offers a single interpretive warning and says nothing about the one input parameter or how results should be trusted or cross-checked with sibling capability tools.

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?

There is one optional parameter, scene_token, at 0% schema description coverage, so the description must compensate and does not. It never explains what a scene token is, what happens when it is omitted (the default is null), or how scoping affects the probe results.

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?

The verb 'Read' and resource 'actual SDK symbol signatures' give a rough sense of a diagnostic probe, and the caveat 'Presence never proves native Cut works' hints at the Cut domain. However, the description never states plainly that it inspects Cut runtime symbol availability, and it does not distinguish itself from siblings such as cut_qt_runtime_capabilities or cut_inspect.

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?

'Presence never proves native Cut works' is an interpretation warning, not when-to-use guidance. The description never says in what situation an agent should call this probe rather than a runtime-capabilities or inspect sibling, and names no alternative.

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