scout-mcp

github_repo_info

Get detailed info about a GitHub repo: stars, forks, contributors, releases, license, topics. Provide owner and repo name to fetch structured data.

Instructions

Get detailed information about a specific GitHub repository: stars, forks, contributors, releases, license, topics, and more.

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": {
      "owner": "<owner>",
      "repo": "<repo>"
    },
    "name": "github_repo_info"
  }
}

Input Schema

Name	Required	Description
`owner`	Yes	Repository owner (user or org)
`repo`	Yes	Repository name
`include_contributors`	No	Include top 10 contributors
`include_releases`	No	Include 5 most recent releases

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 23, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It correctly implies a read-only operation by listing fetched data and uses conditional boolean parameters. However, it does not mention rate limiting, authentication, or any potential side effects, which is acceptable for a typical read-only data retrieval tool.

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?

The description is a single concise sentence that lists key functionalities. It is front-loaded and contains no redundancy.

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?

The tool is relatively simple with four parameters, all documented. The description lists the key data fields returned. Since there is no output schema, the description compensates by summarizing the output. It is fully adequate for the tool's complexity.

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?

The schema has 100% description coverage, so all parameters are documented in the schema. The description adds high-level context by listing data fields but does not add syntax or format details beyond the schema.

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?

The description explicitly uses 'Get detailed information' as the verb and clearly identifies the resource ('specific GitHub repository'). It lists specific data fields (stars, forks, contributors, releases, license, topics) and distinguishes itself from sibling tools like 'github_search', which presumably searches for repositories.

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 usage for retrieving repo details, but it does not explicitly state when to use this tool versus alternatives. Given sibling tools like 'github_search', 'scout_report', and others, there is no guidance on choosing this tool over them.

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