Skip to main content
Glama

Read one outlook's odds and readings

get_outlook
Read-onlyIdempotent

One standing forecast: the odds Frontier Desk gives every path at each of the two dates it is scored on, the readings behind them, the scenarios with the markers that say which one we are on, and when it is next rescored. Odds come from a simulation of chained steps and are the desk's own; they are not a market price and nothing settles them but the dated public sources each report names. The whole report is on its page.

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": {
      "outlook": "<outlook>"
    },
    "name": "get_outlook"
  }
}

Input Schema

NameRequiredDescriptionDefault
outlookYesThe outlook's route, as list_outlooks gives it: /outlook/company-data-market-2027, /outlook/ai-jobs-and-income-2035, /outlook/compute-financing-2028, /outlook/data-center-power-2028, /outlook/private-credit-lower-middle-market-2028, /outlook/accounting-firm-rollups-2028, /outlook/insurance-agency-consolidation-2028, /outlook/autonomous-companies-2028, /outlook/nvidia-without-its-founder-2027.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / outlook / description
      Previous value: -"The outlook's route, as list_outlooks gives it: /outlook/company-data-market-2027, /outlook/ai-jobs-and-income-2035, /outlook/compute-financing-2028, /outlook/data-center-power-2028, /outlook/private-credit-lower-middle-market-2028, /outlook/accounting-firm-rollups-2028, /outlook/insurance-agency-consolidation-2028, /outlook/autonomous-companies-2028."New value: +"The outlook's route, as list_outlooks gives it: /outlook/company-data-market-2027, /outlook/ai-jobs-and-income-2035, /outlook/compute-financing-2028, /outlook/data-center-power-2028, /outlook/private-credit-lower-middle-market-2028, /outlook/accounting-firm-rollups-2028, /outlook/insurance-agency-consolidation-2028, /outlook/autonomous-companies-2028, /outlook/nvidia-without-its-founder-2027."
    • changedInput schema / properties / outlook / enum
      Previous value: -[
      -  "/outlook/company-data-market-2027",
      -  "/outlook/ai-jobs-and-income-2035",
      -  "/outlook/compute-financing-2028",
      -  "/outlook/data-center-power-2028",
      -  "/outlook/private-credit-lower-middle-market-2028",
      -  "/outlook/accounting-firm-rollups-2028",
      -  "/outlook/insurance-agency-consolidation-2028",
      -  "/outlook/autonomous-companies-2028"
      -]New value: +[
      +  "/outlook/company-data-market-2027",
      +  "/outlook/ai-jobs-and-income-2035",
      +  "/outlook/compute-financing-2028",
      +  "/outlook/data-center-power-2028",
      +  "/outlook/private-credit-lower-middle-market-2028",
      +  "/outlook/accounting-firm-rollups-2028",
      +  "/outlook/insurance-agency-consolidation-2028",
      +  "/outlook/autonomous-companies-2028",
      +  "/outlook/nvidia-without-its-founder-2027"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful semantics beyond that: the odds are simulation output from chained steps, are the desk's own rather than a market price, and nothing settles them except the dated public sources. It does not cover error behavior for an invalid route or pagination/format, so it is solid but not rich.

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?

It is front-loaded with the resource and its contents, but the phrasing is ornate and some clauses are vague ('the markers that say which one we are on'). Two long sentences carry real information yet could be tightened without loss.

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?

With no output schema, the description must convey what comes back, and it does: two dated odds per path, supporting readings, scenario markers, and the next rescore time. It stops short of describing the shape of that payload or how the odds are expressed, which for a single-parameter read is a minor gap.

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?

Schema coverage is 100% and the enum plus its description already enumerate every valid route and point to list_outlooks. The prose adds nothing about the 'outlook' parameter itself, so the baseline of 3 applies.

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 names the resource precisely ('One standing forecast') and enumerates its contents: odds at two scored dates, the readings behind them, scenarios with markers, and the next rescore date. It is clearly a single-outlook read rather than a list, though the verb is only implicit (the title carries 'Read') and no sibling such as list_outlooks is named.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no pointer to list_outlooks as the way to discover valid routes. The single required argument and the enum make the call pattern obvious by inference, but the description itself supplies no routing advice.

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