Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

md_capabilities

Read packaged capability declarations to see which MD MCP Plugin features are declared; this does not verify runtime support or live validation.

Instructions

Read packaged capability declarations. Does not prove runtime support or successful live validation.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 behavioral burden, and it does disclose one valuable trait beyond the name: the result is a static declaration, not evidence of live runtime support. However, nothing is said about what is returned (a list? a map?), whether results are scoped or filtered, or any freshness/caching characteristics of 'packaged' data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, and the positive definition is front-loaded ahead of the limitation caveat. Every sentence earns 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 output schema and no annotations, the description is the only source of information about the return value, and it never describes what a 'capability declaration' looks like or how results are organized. The scope it does provide (static, not runtime-proof) is useful but not sufficient for a zero-parameter read tool whose only value is its payload.

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 semantics to explain; baseline 4 applies. The empty schema is self-evident and the description does not need to add anything here.

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?

Uses a specific verb+resource pair ('Read packaged capability declarations'), and 'packaged' implicitly distinguishes it from the runtime-capability siblings (canvas_runtime_capabilities, curve_runtime_capabilities, etc.). It falls short of 5 because the subject of the declarations (which host/tool family) is never stated and no sibling is named explicitly.

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 caveat 'Does not prove runtime support or successful live validation' implicitly tells the agent when *not* to rely on this tool, which is real guidance. But it never says when to use it, nor names the runtime-capability alternative the agent should call instead for live validation.

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