Skip to main content
Glama

GitHub trending (x402)

github_trending

Read-onlyIdempotent

$0.09 via x402: top trending GitHub repositories by stars over the last day/week/month, optional language filter. Live from the GitHub Search API.

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

Input Schema

NameRequiredDescriptionDefault
topNo1-30
sinceNoday|week|month
languageNoProgramming language filter, e.g. typescript
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, open world), so the description's added value is real: it discloses the $0.09 x402 cost and the live upstream source. Notably absent is what happens if payment is omitted or fails, though the x_payment schema field says to omit it for terms first.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the cost and source front-loaded and zero filler. Every clause carries information an agent needs: cost, resource, sort key, time window, filter, and provenance.

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, four-optional-parameter lookup with no output schema, this covers the essentials: what is returned (top repos ranked by stars), the time dimension, and the payment requirement. The one gap is that the return shape (fields per repo) is only implied rather than stated, and failure behavior on unpaid calls is left to the schema.

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 four parameters are already documented, including the '1-30', 'day|week|month', and language examples. The description restates the since and language dimensions but adds no syntax or default detail beyond the schema, which is the expected baseline here.

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 resource and scope: 'top trending GitHub repositories by stars over the last day/week/month', plus the data source ('Live from the GitHub Search API'). This is unambiguous and no sibling tool covers GitHub, so differentiation is implicitly clear, though it never names an alternative for contrast.

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 explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The only selection signal is implicit in the word 'trending', leaving an agent to infer that this is for discovery of popular repos rather than, say, searching a specific repo.

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