Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

github_trending_repositories

Fetch GitHub trending repositories by language, spoken language, and daily/weekly/monthly range to identify popular projects.

Instructions

github: Trending Repositories. GET /v1/github/trending/repositories. Get GitHub trending repositories. Supports language, spoken_language_code, and daily/weekly/monthly range filters. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": "github_trending_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoTrending range: daily, weekly, or monthly. Defaults to daily.
languageNoOptional coding language, e.g. javascript, python, or go.
spoken_language_codeNoOptional spoken language code filter, e.g. en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a good job on the cost model: 1 credit on success, no charge for errors, blocked/timed-out requests, invalid requests, or cache hits. It leaves out return shape, auth requirements, and pagination/result limits, which are meaningful for a list endpoint.

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 name, endpoint, and purpose, followed by filters then cost. The two cost sentences are slightly repetitive ('Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing' plus the not-found caveat) but each carries real information.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description is the only source of behavior, and it omits what the response looks like (fields per repository, result count limits). For a simple three-optional-parameter read endpoint this is adequate but not complete.

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%, so all three parameters are already documented with examples and the default. The description only restates the filter set without adding syntax or behavioral nuance (e.g. how an unknown language is handled), so baseline 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?

States a specific verb and resource ('Get GitHub trending repositories') plus the underlying endpoint, which cleanly separates it from repositories-of-a-user siblings like github_user_repositories and from github_trending_developers. It stops short of explicitly naming an alternative, but the resource itself removes ambiguity.

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 implied by the listed filters ('Supports language, spoken_language_code, and daily/weekly/monthly range filters'), and the default of daily is clear. There is no explicit when-to-use/when-not guidance or pointer to a sibling for non-trending repository lookups.

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

Deploy Server

Other Tools