Gluecron

gluecron_search_repos

Read-only

Search repositories by owner, name, owner/name or description, case-insensitively: every public repo, plus the private ones you own or collaborate on when authenticated. Omit query (authenticated) to list YOUR repositories — the ones you own or were invited to — instead of searching. Mirrors GET /api/v2/search/repos. total is the full match count (not the page size) and nextOffset pages through it.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	stars \| updated \| name (default: stars)
`limit`	No	Max rows per page (default 30, max 100)
`query`	No	Search keyword — matches owner login, repo name, owner/name and description. Omit to list your own repositories.
`offset`	No	Rows to skip. Use `nextOffset` from the previous response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026

changedInput schema / properties / query / description

Previous value: -"Search keyword"New value: +"Search keyword — matches owner login, repo name, owner/name and description. Omit to list your own repositories."

removedInput schema / required
```
Removed value: -[
-  "query"
-]
```

Changed2 schema fields changedSep 1, 2026

changedInput schema / properties / limit / description

Previous value: -"Max results (1-100, default 30)"New value: +"Max rows per page (default 30, max 100)"

addedInput schema / properties / offset

Added value: +{
+  "description": "Rows to skip. Use `nextOffset` from the previous response.",
+  "type": "number"
+}

First observedJul 14, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already mark the tool read-only and non-destructive, and the description adds real value by disclosing case-insensitive matching, the authenticated scope for private repos, and pagination semantics: `total` is the full match count and `nextOffset` drives paging. No statement contradicts the annotations.

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 dense sentences, with the core action and scope front-loaded and every clause earning its place. It packs mode selection, auth scope, API mapping, and pagination semantics without waste.

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?

For a tool with no output schema, the description fills the important gaps: auth requirements, search scope, the list-my-repos mode, and pagination via `nextOffset` and `total`. The remaining details like sort defaults and max limit are already in the schema, so nothing essential is missing.

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%, so the schema already documents all four parameters, which sets a baseline of 3. The description reinforces the `query` behavior by explaining the omit-to-list mode and case-insensitivity, but adds little about `sort`, `limit`, or `offset` beyond what the schema already says.

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 opens with a specific verb and resource: 'Search repositories by owner, name, owner/name or description' and clearly defines the scope: every public repo plus authenticated private repos. It does not explicitly contrast with the similarly named sibling gluecron_repo_search, so some sibling differentiation is left to inference.

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 an explicit mode rule: omit `query` (when authenticated) to list YOUR repositories instead of searching, and notes that private repos are only included when authenticated. It does not name alternative tools or say when to prefer a sibling, which is the main gap.

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

All Gluecron tools Inspect

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

Need Help?