Skip to main content
Glama

Daily brief

get_brief
Read-only

Free, Standard and Pro: the daily brief of a completed UTC day (latest by default; day YYYY-MM-DD from available_from): a cited headline and paragraphs, the day's closing sentiment, lead, top and other stories, and the developing event. Each paragraph lists citations (phrase, story_id, reader_url); cite those story ids. Today's brief is written shortly after 00:00 UTC; 404 for unwritten days. English.

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

Input Schema

NameRequiredDescriptionDefault
dayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover readOnly/openWorld; the description adds the tier availability (Free/Standard/Pro), the 00:00 UTC publication timing, the 404 behavior for unwritten days, the English-only constraint, and the citation contract (phrase, story_id, reader_url) with an instruction to cite story ids.

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 tier and scope, then contents, then citation handling and failure timing. Dense but every clause carries information; the long parenthetical enumeration of returned sections is the only borderline-redundant part.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 still tells the agent exactly what a successful response contains and how to cite it, plus the failure mode and the default behavior for a single optional parameter. Nothing needed to invoke it correctly is missing.

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 description coverage is 0%, so the description must carry the meaning: it explains that omitting day returns the latest brief, that day is a YYYY-MM-DD date bounded by available_from, and that unavailable days produce 404. Only minor format detail is repeated rather than added.

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?

States a specific verb and resource — the daily brief for a completed UTC day — and enumerates contents (headline, paragraphs, closing sentiment, lead/top/other stories, developing event), which clearly separates it from the story- and sentiment-level siblings.

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?

Gives concrete calling guidance: latest by default, optional day in YYYY-MM-DD form drawn from available_from, and a 404 for unwritten days. It stops short of explicitly saying when to prefer this over siblings like get_developing or get_sentiment, so it is clear context rather than full routing.

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.