Skip to main content
Glama
github-fetcher

github-fetcher

by KurvCygnus

GitHub user search

github_search_users
Read-onlyIdempotent

Search GitHub users by location, language, followers, or repository count to identify developers matching specific criteria. Returns paginated results with login, type, and profile URL.

Instructions

Search GitHub users by query syntax — location, language, followers:>=N, repositories:>=N, fullname: qualifiers. Costs 1 search call; the search quota is 30 requests per minute. Returns {total_count, incomplete_results, items[{login, type, html_url}], page, per_page, has_more, next_page}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "github_search_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1
sortNoSort field: followers, repositories, or joined
freshNoBypass the local cache
orderNoSort order: asc or desc
queryYesGitHub user search syntax, like location:china followers:>=10 repositories:>=8
per_pageNoItems per page, 1-100, default 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • changedInput schema / properties / order / description
      Previous value: -"Sort order"New value: +"Sort order: asc or desc"
    • changedInput schema / properties / sort / description
      Previous value: -"Sort field"New value: +"Sort field: followers, repositories, or joined"
  2. Addedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered; the description adds genuinely new operational context by disclosing the cost model (1 search call) and the 30 requests/minute quota. It also spells out the exact response envelope including pagination fields. It stops short of explaining that `fresh` bypasses the local cache, which is the one behavioral lever left undocumented.

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?

Three front-loaded sentences: purpose plus syntax first, then cost and quota, then the return contract. No filler, no restating of the title, and the return-shape sentence earns its place because no output schema exists.

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

Completeness5/5

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

With six parameters, an absent output schema, and full schema coverage, the description covers exactly what structured data cannot: query syntax breadth, rate-limit cost, and the response envelope. An agent has everything needed to construct a call and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so a baseline of 3 applies, and the description earns one step above it by enumerating qualifiers (`language`, `fullname`) that the schema's `query` description does not mention. It adds no meaning for the pagination, sort, order, or fresh parameters, which remain schema-only.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search GitHub users') and immediately scopes it with the qualifier syntax that defines this tool's search domain (location, language, followers, repositories, fullname). The resource noun 'users' cleanly separates it from github_search_code, github_search_repos, and github_search_issues without needing to name them.

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 resource ('search users'), but the description never states when to prefer this over a direct lookup sibling like github_user for a known login, nor any exclusion such as cache behavior despite the `fresh` parameter. The quota line tells the agent about budget pressure but is not routing guidance.

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