Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

curve_runtime_capabilities

Reads actual API symbols and the trusted writer's availability so clients can verify runtime capabilities without editing geometry.

Instructions

Read actual API symbols and the trusted writer's availability; never edits geometry.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the most important trait: this is a pure read that will not mutate geometry. It says nothing about cost, side effects, failure modes when the trusted writer is unavailable, or what the response contains, so the disclosure is partial.

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 read-only guarantee front-loaded and no filler. It is arguably too terse for a tool with no output schema, but nothing in it is redundant.

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-parameter probe this is close to adequate, but with no output schema and no annotations the description is the only source of information about what comes back, and it never describes the return shape or what 'trusted writer's availability' means in practice.

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 add 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.

Purpose3/5

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

The description names a read verb and two things it reports ('actual API symbols' and 'the trusted writer's availability'), which is more than a restatement of the name. However, 'API symbols' is unexplained jargon and the agent cannot tell what a symbol record looks like or how this differs from sibling probes such as canvas_runtime_capabilities or md_capabilities beyond the 'curve' prefix.

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 statement of when to call this versus curve_handles, md_capabilities, or the other *_runtime_capabilities probes. The only guidance is the negative constraint 'never edits geometry', which implies a when-not but gives no positive trigger condition or prerequisite.

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