Skip to main content
Glama

show_report_card

Read-only

Show a QuanterLab report as a card in the chat: what was compared, the test's figures beside simply holding the same asset, and a growth-of-$1 chart (for a stochastic run with a parameter grid, the grid of each setting's Sharpe with the best one outlined, its cells in grid), a button to open the full report, and the card's next steps as choices a tap puts in the chat, with one to change a setting (on a lab run, the choices open the project in the lab, where the change is made). It is for a report with no card in the chat yet: the link summarize_workflow or save_workflow_result answered with (a backtest, walk-forward, stochastic backtest, regime analysis or optimization, scan or lab run), or a report link the person pastes. A run started in this chat shows its result in its own card, so the report_url a start or its progress tool answered with needs no second card. One call shows the card, and the card offers the report's next steps as choices. The card shows what was compared and the figures; say what the result means in your own words.

    Args:
        report_url: the link summarize_workflow or save_workflow_result answered with
            (https://quanterlab.com/r/..., /report/..., /backtest-report/... or /filter-report/...), or a
            report link the person pastes.
    

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": {
      "report_url": "<report_url>"
    },
    "name": "show_report_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful context beyond them: one call renders the card, the card contains comparisons, figures, a chart, next-step choices, and different grid behavior for stochastic runs. It does not cover error behavior, so it is not a 5.

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

Conciseness3/5

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

The purpose is front-loaded, but the description is a long run-on with nested parentheticals and some repetition. It remains usable, yet several clauses could be tightened without losing information.

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

Completeness5/5

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

For a one-parameter, read-only display tool with no output schema, the description covers the trigger conditions, the input source, what the card displays, how it differs from run-result cards, and post-call guidance to interpret results in the agent's own words. It is complete enough for correct invocation.

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

Parameters5/5

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

The only parameter, report_url, has 0% schema description coverage, but the description compensates strongly by naming accepted URL forms (/r/, /report/, /backtest-report/, /filter-report/) and sources (summarize_workflow, save_workflow_result, or a pasted link).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description states a specific verb and resource: show a QuanterLab report as a card in the chat. It also distinguishes this tool from run-result cards and from summarize_workflow/save_workflow_result, so an agent can identify its role without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit when-to-use criteria: a report with no card yet, a link returned by summarize_workflow or save_workflow_result, or a pasted report link. It also explicitly excludes run results that already have their own card, naming the relevant progress/start tools.

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