Skip to main content
Glama

foresea_track_record

Check Foresea's forecast reliability by returning accuracy, Brier score, calibration error, and skill-vs-market results across time horizons, so you can decide whether to trust a forecast.

Instructions

Call this when the user asks how reliable or accurate Foresea is, or wants to know whether to trust a forecast. Good triggers: "How good is Foresea?", "What's the track record?", "Has it been right before?", "Is it calibrated?", "What's the Brier score?". Returns accuracy, Brier score, calibration (ECE), and skill-vs-market broken down by time horizon. Pass optional fields list (e.g. ['brier_score', 'accuracy', 'n_snapshots_resolved']) to reduce token usage.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden; it discloses the output dimensions (accuracy, Brier, ECE, skill-vs-market by time horizon) and a token-usage optimization behavior via the fields argument. It does not state read-only status, rate limits, or auth needs, which is the remaining gap.

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?

Front-loaded with the trigger condition, followed by return values and the parameter hint; each part is useful. The enumerated return list slightly duplicates the output schema, but the trigger phrases and token-saving tip earn their space.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes them and covers triggers and the optional parameter. For a zero-required-parameter read tool this is close to complete; minor gaps are auth/rate-limit context.

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% (the single 'fields' param has no description), so the description must compensate. It does, by explaining the argument is an optional list of field names and giving concrete example values ('brier_score', 'accuracy', 'n_snapshots_resolved') and the purpose (reduce token usage).

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 meta-resource (Foresea's own accuracy/track record) and enumerates the returns: accuracy, Brier score, calibration (ECE), and skill-vs-market by horizon. This clearly separates it from sibling tools, which operate on market data rather than Foresea's own reliability.

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 an explicit when-to-use condition (user asks how reliable/trustworthy Foresea is) plus four concrete trigger phrases ("How good is Foresea?", "What's the track record?", "Has it been right before?", "What's the Brier score?"). An agent can match intent to this tool without inference.

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