Skip to main content
Glama
websearch-mcp

websearch-mcp

by xronocode

search_github

Read-onlyIdempotent

Find GitHub repositories by topic, name, or description, and search issues for bug reports and discussions without an API key; uses local caching for repeated queries.

Instructions

Free LOCAL GitHub search via the official REST API, no key needed (set GITHUB_TOKEN env for higher limits). kind='repos': find repositories by topic/name/description (sorted by stars). kind='issues': bug reports and discussions. Useful to find tools, code examples, whether something is maintained. Cached 24h.

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

Input Schema

NameRequiredDescriptionDefault
kindNorepos
queryYes
max_resultsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.8/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 safety is covered. The description adds genuinely new behavioral facts: no API key required, GITHUB_TOKEN raises rate limits, and results are cached for 24h (a real staleness caveat). It does not say what happens on rate-limit exhaustion or how caching is invalidated.

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?

Front-loaded with the core capability and cost model, then kind-specific details, then use cases. Dense but nearly every clause adds information; only the parenthetical token note could be trimmed slightly.

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?

An output schema exists, so return shapes need not be described. Combined with annotations covering safety and the description covering auth/rate limits, caching, and kind semantics, an agent has enough to call this correctly; only max_results remains unexplained, a minor gap for a defaulted integer.

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 0% and there are no enums, so the description carries the burden. It documents 'kind' well ('repos' vs 'issues' with sort-by-stars and content type) but leaves 'query' syntax (e.g., whether GitHub qualifiers work) and 'max_results' semantics undocumented.

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 verb and resource — GitHub repository/issue search via the official REST API — and splits behavior by the 'kind' value. It is distinguishable from search_news or search_semantic by the explicit 'GitHub' scoping, though it never names the generic 'search' sibling to contrast with.

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?

Gives use cases ('find tools, code examples, whether something is maintained') which implies when to reach for it, but offers no explicit when-not guidance and no routing against the sibling 'search'/'fetch' tools. The agent must infer that this is the GitHub-specific path rather than general web search.

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