Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

github_trending_developers

Retrieve GitHub trending developers filtered by programming language and daily, weekly, or monthly range to identify active contributors.

Instructions

github: Trending Developers. GET /v1/github/trending/developers. Get GitHub trending developers. Supports language 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_developers"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoTrending range: daily, weekly, or monthly. Defaults to daily.
languageNoOptional trending coding language, e.g. javascript, python, or go.

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 supplied, the description carries the full burden and does a fair job by disclosing the billing model: 1 credit on success, nothing for errors, blocked, timed-out, invalid, or cache-hit requests. That is genuinely useful pre-call context an agent cannot get from structured fields. It omits return shape, result size, and any rate-limit or auth notes, so it is not exhaustive.

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?

The opening is front-loaded but redundant: the title fragment, the raw route, and 'Get GitHub trending developers' all say the same thing before any filters or cost details appear. The cost sentences do earn their place, but roughly a third of the text is duplication.

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 two-optional-parameter read endpoint with 100% schema coverage and no output schema, the description covers purpose, filters, and billing, which is what an agent needs before calling. What is missing is any indication of the response payload (a list of developers with what fields?) or whether results are paginated or limited.

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 both parameters (since, language) are already fully documented with examples and the default. The description only restates that language and daily/weekly/monthly range filters exist, adding no syntax or semantics beyond the schema; 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?

The description names a specific verb and resource ('Get GitHub trending developers') plus the underlying route, which cleanly separates it from the sibling github_trending_repositories. It stops short of explicitly contrasting itself with that sibling, but the resource noun does the disambiguation work.

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: the agent can infer you call this to see who is trending on GitHub, optionally scoped by language and time range. There is no explicit when-to-use statement, no when-not to use it, and no mention of the closest alternative (trending repositories).

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