Skip to main content
Glama

get_weekly_digest

Read-only

Get a HotRepo weekly digest, the weekly email also published on hotrepo.ai/weekly: an editorial introduction (a headline and a few themes), the week's 10 biggest gainers, notable new repositories, and each day's top gainer. stars_that_week is the highest star count seen that week, not today's count. daily_top_gainers lists, for each day, the repository that gained the most stars that day among those on GitHub's all-languages daily Trending with a published HotRepo review; it is not necessarily the one GitHub showed at #1. The top list comes from GitHub's weekly Trending; when fewer than 10 usable repositories were on it, it is topped up with the biggest gainers summed over that week's daily Trending boards. Each top item's ranked_from says which ("weekly_trending" or "daily_trending_sum"; null on older issues where the issue-level top_source is "mixed"). Do not call a daily_trending_sum item part of the weekly Trending. Lists were fixed when the issue went out; repositories later removed by HotRepo are dropped and the rest renumbered, and ones without a published review link to GitHub (url is null).

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

Input Schema

NameRequiredDescriptionDefault
weekNoISO week such as 2026-w45 (the week starting that Monday, UTC); omit for the latest issue. Earlier issues need Pro (Free: latest issue only)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description goes far beyond that with snapshot semantics ('Lists were fixed when the issue went out'), mutation caveats (removed repos dropped and renumbered, url null without a published review), and the exact composition rule for the top list including top-up behavior. It also pre-empts a common misreading of stars_that_week as a current count.

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 purpose, but the remainder is a dense block of field-level prose with no breaks, and much of it (stars_that_week, daily_top_gainers, ranked_from) overlaps with what an output schema is meant to carry. Sentences earn their place individually, but the whole is harder to scan than its length warrants.

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 read-only digest tool with a full output schema, this covers nearly everything that matters: list provenance, snapshot immutability, null handling, and the ranked_from values with the legacy 'mixed' case. The only gap is how it relates to the sibling report/trending tools for choosing between them.

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% and the single week parameter is already fully documented there, including the ISO format example and the Free-vs-Pro access rule, so the baseline of 3 applies. The description adds no additional detail about the parameter's format or edge cases.

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 first sentence states a specific verb and resource ('Get a HotRepo weekly digest') and enumerates the payload (editorial intro, 10 biggest gainers, notable new repos, daily top gainers), so the agent knows exactly what this returns. It never explicitly contrasts with the analogous sibling get_monthly_report or get_trending, so sibling differentiation is left to the name.

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

Usage Guidelines3/5

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

Usage is only implied: 'omit for the latest issue' and the Pro restriction live in the schema, not the description. The one explicit directive ('Do not call a daily_trending_sum item part of the weekly Trending') governs how to report results rather than when to call the tool. There is no statement of when to prefer get_monthly_report, get_trending, or get_star_history instead.

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