Skip to main content
Glama
Sign In

ScrapeIO

by com.scrapeio
OverviewDiscussionsAdmin

github_trending_repositories

Read-only

GitHub's trending repositories, with stars gained in the period. (1 credit)

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
sinceNodaily, weekly or monthly.
languageNoProgramming language, e.g. typescript.
spoken_language_codeNoSpoken language, e.g. en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely new information in the form of a cost signal ('1 credit') and the ranking basis (stars gained in the period), but says nothing about result volume, ordering, or default period behavior.

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?

Two short, front-loaded fragments with zero filler; the resource is stated before the qualifier and the cost flag.

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?

For a simple read-only lookup this is near-adequate, but with no output schema the description omits what a returned entry looks like (repo fields, rank, star deltas) and what the default `since` value is when omitted.

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% with all three optional parameters documented, so the baseline is 3. The description adds no extra meaning about how `since` or language filtering interacts with the trending window.

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 states a specific resource ('GitHub's trending repositories') and adds scope detail ('stars gained in the period'). The word 'repositories' implicitly separates it from github_trending_developers, but no sibling is named directly, so it falls short of a 5.

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 guidance on when to choose this over the other GitHub tools (developers, user contributions) or any prerequisites/exclusions. The agent must infer usage purely from the name and resource noun.

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

All ScrapeIO toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources