Skip to main content
Glama

captapi

by io.github.CDCStream
OverviewDiscussionsAdmin

github_trending_developers

github.com/trending/developers — windowed ranks with popularRepo + followers (2 credits). Costs 2 credits. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cacheNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.
limitNoMax items to return (default 25, max 100). Flat 2 credits per call.
sinceNoTrending window: daily (default), weekly, or monthly — matches github.com/trending/developers?since=.
languageNoOptional programming-language slug → /trending/developers/{language}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh."
  2. Changed4 schema fields changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache. Default false — always fetch fresh data."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."
    • changedInput schema / properties / language / description
      Previous value: -"Optional programming-language slug, e.g. python."New value: +"Optional programming-language slug → /trending/developers/{language}."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 25, max 100. Flat 2 credits per call."New value: +"Max items to return (default 25, max 100). Flat 2 credits per call."
    • changedInput schema / properties / since / description
      Previous value: -"daily (default), weekly, or monthly."New value: +"Trending window: daily (default), weekly, or monthly — matches github.com/trending/developers?since=."
  3. Changed5 schema fields changed
    • addedInput schema / properties / language
      Added value: +{
+  "description": "Optional programming-language slug, e.g. python.",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 100. Billed per result."New value: +"Max items to return. Default 25, max 100. Flat 2 credits per call."
    • removedInput schema / properties / q
      Removed value: -{
-  "description": "GitHub user search query. Default followers:>1000.",
-  "type": "string"
-}
    • addedInput schema / properties / since
      Added value: +{
+  "description": "daily (default), weekly, or monthly.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "q"
-]
  4. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true)."New value: +"Set true to serve from the 24h response cache. Default false — always fetch fresh data."
  5. Changed1 schema field changed
    • addedInput schema / properties / cache
      Added value: +{
+  "description": "Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true).",
+  "type": "boolean"
+}
  6. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does meaningfully disclose cost (2 credits), free handling of empty results/failures, and cache semantics with a fresh-by-default policy. It does not cover rate limits or response shape, but it adds substantial non-obvious behavioral context beyond the basic operation.

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?

The description is compact and front-loaded with the endpoint and key semantics, followed by billing/cache caveats. It is slightly redundant in stating the 2-credit cost twice, but it remains efficient and scannable.

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 simple, fully optional-parameter fetch tool, the description covers the source, return content, pricing, failure charging, and caching behavior. It lacks an explicit output shape, but the 'popularRepo + followers' mention gives the agent enough context to understand what will be returned.

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 the schema already documents cache, limit, since, and language thoroughly. The description reinforces cache behavior and the trending-window concept but adds little parameter meaning beyond what the schema provides.

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 clearly identifies the resource (github.com/trending/developers) and the core output concept: windowed ranks with popularRepo + followers. It distinguishes this from sibling github_trending_repositories by name and content, though it lacks an explicit imperative verb like 'Get' or 'List'.

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?

The description implies when to use it (when you need trending developers, optionally filtered by since window or language), and the since/language parameters provide usage context. However, it does not explicitly state when not to use it or name an alternative such as github_trending_repositories.

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

All captapi 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