Skip to main content
Glama

List the standing outlooks

list_outlooks
Read-onlyIdempotent

Frontier Desk's standing forecasts: what each one forecasts and over what horizon, the day it was published, and the date it is next rescored. Pass a route from here to get_outlook for the odds on every path.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnly, idempotent, non-destructive, closed-world, and with no output schema the description usefully discloses what each record contains, including the derived "next rescored" date, which is non-obvious. It stops short of saying how many outlooks exist or whether results are ordered/paginated.

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

Conciseness5/5

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

Two sentences, front-loaded with the resource and its payload, ending with the handoff to the sibling. No filler or restatement of the title.

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 zero-parameter list with no output schema, describing the returned fields makes the definition essentially complete. Minor gap: no indication of result volume, ordering, or how to page through a long catalog.

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 tool takes no parameters, so the schema baseline is 4. The description correctly implies a parameterless enumeration and adds no misleading parameter talk; the mention of a "route" clearly refers to an argument of get_outlook, not this tool.

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?

"Frontier Desk's standing forecasts" names the specific resource, and the description enumerates the fields each entry carries (what it forecasts, horizon, publication date, next rescore date). The closing routing sentence separates it from get_outlook, which returns odds per path.

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?

Explicitly sets up the discovery-then-fetch chain: this tool supplies routes, and "Pass a route from here to get_outlook for the odds on every path." The agent knows both which tool to call and what to do with its output.

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