The 07:00 Brief

Get risk radar

get_risk_radar

Read-onlyIdempotent

The Risk Radar from The 07:00 Brief: the ranked risks being watched, each with its theme, trend, impact, probability, summary, the indicator to watch, what it would mean for portfolios, when it was first seen and on how many mornings it has appeared. The latest radar also gives when tracking began, how many mornings have been read and how many risks have been tracked. Without a date it is the latest radar; with date (YYYY-MM-DD) it is the radar published that day.

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

Input Schema

Name	Required	Description	Default
`date`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 18, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds useful behavioral context: the default-to-latest behavior and what the latest edition aggregates (tracking start, mornings read, risks tracked). It says nothing about pagination or rate limits, but those are not central here.

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 identity, but the long enumeration of output fields (theme, trend, impact, probability, summary, indicator, portfolio meaning, first-seen, morning count) largely duplicates the existing output schema and inflates the sentence without adding call-time value.

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 single optional-parameter read tool with an output schema and full annotation coverage, the description supplies everything needed to call it correctly, including the date format and default. The return-field enumeration is redundant given the output schema, but nothing an agent needs is missing.

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?

Schema description coverage is 0%, and the description compensates fully: it names the parameter's format (YYYY-MM-DD), its meaning (the radar published that day), and its default behavior (latest radar when omitted). An agent can invoke it correctly from the description alone.

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 states a specific verb and resource — retrieving the ranked Risk Radar risks with their theme, trend, impact and probability — and ties it to 'The 07:00 Brief'. It is clearly a getter for a distinct artifact, but it never explicitly contrasts itself with siblings like get_morning_brief.

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

Usage Guidelines4/5

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

It clarifies the selection rule for the single parameter: no date returns the latest radar, a date returns that day's radar. That is actionable context, though there is no guidance on when to prefer a sibling tool or when this tool is inappropriate.

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

All The 07:00 Brief tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.