Skip to main content
Glama

describe_capability

Read-only

Match a natural-language intent string to one or more QuanterLab workflows.

    Returns a list of matching workflows with their name, description, required and optional parameters, estimated
    runtime, and what a request may leave open with the default each one takes (`defaults`). Use this to pick the
    right `start_*` tool when the user describes what they want in their own words. The run starts with those
    defaults, named in one short line with its result; the person's own changes come after it, as next steps. An
    open question that names no rule, stock or study ("what can you do", "show me something") is answered as
    get_started answers it: one question, what the person would like to test, over three setups from QuanterLab's
    Library, and nothing else; nothing plays before the person picks, also when they leave the choice to you. A
    request to run or see something that names no rule and no stock ("make a backtest", "test something", "show me
    what it does") gets that same answer, never a default rule.

    Args:
        intent: What the person wants, in their own words, e.g. "I want to find mean-reverting
            stocks", "backtest an RSI strategy on Apple", "is my SPY
            strategy overfit?".
    

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "intent": "<intent>"
    },
    "name": "describe_capability"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint false), and the description still adds the concrete return shape: name, description, required and optional parameters, estimated runtime, and defaults. That is useful beyond what the structured fields say, though how defaults are surfaced to the caller is left slightly ambiguous.

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

Conciseness2/5

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

The first two sentences are well front-loaded, but roughly half the text is conversational policy about how to phrase a run's defaults and what to say before a person picks — rules that do not describe what this tool does. That off-topic bulk dilutes the parts an agent needs in order to invoke it.

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, the description is responsible for return values and it does list them, which is the main completeness need for a one-parameter lookup. However, embedded response-ordering and prompting rules push it past what a tool definition should carry, and nothing says what an empty match looks like.

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?

Schema coverage is 0%, so the description carries the full burden, and it does supply meaning plus three worked examples of the intent string ('I want to find mean-reverting stocks', 'backtest an RSI strategy on Apple', 'is my SPY strategy overfit?'). It does not say how vague or multi-intent strings are handled.

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?

Opens with a specific verb and resource: 'Match a natural-language intent string to one or more QuanterLab workflows.' It distinguishes itself from the sibling get_started by contrasting its matching behavior with how get_started answers open-ended questions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use this to pick the right `start_*` tool when the user describes what they want in their own words' gives a clear triggering condition, and the get_started comparison rules out a common alternative. It never states an explicit when-not-to-use case, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources