Skip to main content
Glama

get_started

Read-only

The first contact: what QuanterLab is and what it can do, for a hello, a question about QuanterLab, a request for help, a person with no rule in mind yet, or a request to run or see something that names no rule and no stock (make a backtest, test something, show me what it does). It answers with what QuanterLab does (tests that guard against overfitting, 20 years of daily point-in-time data, S&P 500 tests on the companies that were in the index on each date) and one question, what the person would like to test, over three setups from QuanterLab's Library, picked by their stored results and varied in kind, one tap each; the card also offers a company to look up, the person's own portfolio and a trading idea of their own. Its card is the answer: after it, ask only that question. It starts nothing. A tapped setup plays with start_test from its stored result, card by card, using none of the person's runs, and nothing plays before the person picks, also when they left the choice to you; a rule or a stock of their own is tested as they name it, and an idea of their own is built from the lab's cards in the chat with build_circuit, a year a run unless they name a span. plain says the same in words for a host that shows no cards.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety and scope are covered structurally. The description adds genuinely useful behavior: 'It starts nothing', nothing plays before the person picks, a tapped setup uses none of the person's runs, and it defers to `plain` on card-less hosts. However, it introduces a `plain` option that the empty input schema never declares, which muddies what the agent can actually pass.

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?

Roughly 190 words in two sprawling sentences with nested asides ('card by card, using none of the person's runs, and nothing plays before the person picks, also when they left the choice to you'). The opening clause is reasonably front-loaded, but the density and missing punctuation make it hard to parse on first read, and several clauses could be cut without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter, no-output-schema onboarding tool, the description compensates well: it describes what the returned card contains (capability summary, one question, three varied setups picked by stored results), the one-tap interaction, and what happens downstream via start_test and build_circuit. The main incompleteness is the undefined `plain` mode and the unclear handoff wording ('after it, ask only that question').

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters the baseline would be 4, but the description references a `plain` mode ('says the same in words for a host that shows no cards') that is absent from the schema. That is a real semantic gap for a no-param tool: the agent cannot tell whether `plain` is a parameter, a host capability, or automatic behavior.

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?

The description identifies a specific role: the onboarding/first-contact entry point that answers with a capability summary, one question, and three library setups. It distinguishes itself from siblings by naming start_test for played setups and build_circuit for user-built ideas. The verbs and scope are there, but the run-on phrasing ('the card also offers a company to look up, the person's own portfolio and a trading idea of their own') makes the core purpose harder to extract than it should be.

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?

It gives an explicit trigger list: a hello, a question about QuanterLab, a help request, a person with no rule in mind, or a request that names no rule and no stock. It also draws a boundary by saying a rule or stock the person names is tested as named (via start_test) and an idea of their own goes through build_circuit. What is missing is a crisp negative form ('do not use this when the user has already named a rule or stock').

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