Skip to main content
Glama
Sign In

gitmanual

by io.github.zainudinnoori
OverviewDiscussionsAdmin

Search repos with setup manuals

search_repos
Read-only

Find open-source GitHub repos on gitmanual's shelf: by words in the name or description, by the system they run on, language or difficulty, or only those rising on GitHub this week. Each result links to its setup manual.

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

Input Schema

NameRequiredDescriptionDefault
osNoOnly repos that run on this system.
pageNo
sortNostars (default), recent, popular, or worked (most people got it running).
queryNoWords to look for in the repo's name or description.
risingNoOnly repos rising on GitHub this week.
languageNoMain language, as GitHub names it, e.g. "Python".
difficultyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description reinforces the latter by clarifying the corpus is gitmanual's curated shelf rather than all of GitHub, which is meaningful behavioral context. It also discloses a return-shape detail (results link to setup manuals). It omits result limits and pagination 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 sentences, front-loaded with the core purpose and scope, then the searchable facets and the result property. No filler or redundant restatement of the tool name.

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?

With seven optional parameters, no output schema, and no required fields, the description does enough to convey the discovery role, the corpus boundary, and what each hit contains. The only gaps are pagination behavior for 'page' and the meaning of the 'sort'/'worked' option, though the schema covers both.

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?

At 71% schema coverage the schema already documents most parameters, including the sort enum semantics. The description mirrors the facets (system, language, difficulty, rising this week, words in name/description) but adds no syntax or format detail beyond the schema, and leaves 'page' and 'sort' unmentioned.

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 ('Find open-source GitHub repos') and immediately bounds the scope ('on gitmanual's shelf'), then enumerates the facets it can be searched by. It is clearly distinguishable from the get_* siblings, which retrieve a single known repo or manual rather than discovering repos.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives concrete usage context by listing the search dimensions (name/description words, system, language, difficulty, rising this week) and hints at the follow-up workflow with 'Each result links to its setup manual', pointing toward get_setup_manual. It stops short of explicit when-not-to-use guidance or naming alternatives like find_alternatives.

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

All gitmanual toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources