Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

cut_qt_runtime_capabilities

Reads trusted provider configuration to inspect available Qt runtime settings without selecting or cutting.

Instructions

Read trusted provider configuration only; never selects or cuts.

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_qt_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
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the critical trait: this is a pure read with no selection or cut side effects. It stops there, saying nothing about whether results are cached, trusted-provider gating, or failure modes when the provider is unavailable.

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 clause with no filler, and the read-only constraint is front-loaded. It is arguably too terse rather than too long, which is a completeness issue handled elsewhere.

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?

For a zero-param, no-output-schema tool the bar is modest, and the safety profile is covered. What is missing is any hint of what "capabilities" data comes back, which an agent needs to decide whether calling it is worth a turn.

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 nothing for the description to disambiguate. Baseline applies, and the description contains no misleading parameter claims.

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 provider configuration only" gives a verb (read) and a resource (provider configuration), but the tool's name promises "runtime capabilities" and the description never says it reports capability information. An agent learns it is a passive read, not what it returns.

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?

"never selects or cuts" functions as an exclusion, implicitly routing cutting work to cut_qt_execute_selected, but there is no positive statement of when an agent should call this. Usage is implied by the read-only framing rather than stated.

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