Skip to main content
Glama

Distribute Software

Today's briefing

get_today
Read-onlyIdempotent

Today's top technology stories (UTC), mixed across Hacker News, newsrooms and Reddit the way the site ranks them, the AI labs' releases of the last two days, and the companies with the most coverage this week. Early in the UTC day it returns yesterday.

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": {
      "context": "<context>"
    },
    "name": "get_today"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), and the description adds genuinely new behavior: UTC day boundaries, a fallback where early-in-the-day calls return yesterday's briefing, and fixed lookback windows (two days of releases, one week of company coverage). It does not mention pagination or payload size, but the temporal semantics are the harder part and are disclosed.

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 content inventory, and the second short sentence carries the one non-obvious edge case. The comma-separated content list is dense but every clause names a distinct section of the return value, so nothing is wasted.

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 has to convey what comes back, and it does so by naming the three section types and their time windows. An agent knows what to expect without a return schema; only the response shape/format (and whether sections can be empty) is left unstated.

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 description coverage is 100%, so all three parameters (context, llm_model, conversation_id) are already fully documented as analytics fields. The description adds nothing about parameters, which is acceptable given the schema does the work, but it earns no credit beyond baseline.

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 enumerates the exact contents returned: top technology stories from HN/newsrooms/Reddit in site-rank order, AI lab releases from the last two days, and most-covered companies this week. That is specific enough to distinguish it from siblings like get_releases or trending_questions, though it states contents as a noun list rather than with an explicit verb like 'returns'.

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 when-to-use guidance and no named alternatives; it never says to prefer this over search_stories or trending_questions for a general overview. The only conditional statement is about time-boundary behavior, not about tool selection.

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