Skip to main content
Glama

Forward scorecard

get_scorecard
Read-onlyIdempotent

Do 3★+ traders' signals, copied at $10, beat matched 2★ ones? The pre-registered forward test (/api/v1/scorecard); ready false until powered. <=1.5 KB.

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_scorecard"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: this is a pre-registered test, the response carries a ready flag that stays false until powered, and the payload is capped at <=1.5 KB — all useful for deciding whether a call is worth making.

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?

Three compact fragments, front-loaded with the research question and then the endpoint, readiness condition, and size cap. It is efficient, though the telegraphic style ("<=1.5 KB", the question-as-purpose) trades some precision for brevity.

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?

There is no output schema, so the description should hint at what comes back; it discloses the ready flag and the size bound but not the scorecard's actual contents (metrics, cohorts, sample sizes). For a zero-parameter read tool this is workable but leaves the returned structure partly opaque.

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 schema has zero parameters, so there is no parameter semantics for the description to compensate for; the baseline of 4 applies. The description correctly implies the call is parameterless and fixed to a single comparison.

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 frames the tool as a question ("Do 3★+ traders' signals, copied at $10, beat matched 2★ ones?") and names the resource as a "pre-registered forward test (/api/v1/scorecard)", so an agent can infer it retrieves scorecard data for a rating-comparison experiment. However, no verb states what the call actually does, and the comparison framing is more evocative than declarative.

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?

"ready false until powered" communicates an important precondition: results are not usable until the test reaches statistical power, which tells the agent to expect a not-ready state. There is no guidance on when to prefer this over siblings such as get_rating_changes or explain_rating, and no explicit exclusion.

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