Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

github_repo_view

Read-only

Fetch GitHub repository metadata via optional authenticated gh CLI to inspect repository details and support Git/GitHub workflow tasks.

Instructions

Show GitHub repository metadata through optional authenticated gh CLI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that — the dependency on the gh CLI and that authentication is optional — but it does not say what happens when gh is missing or unauthenticated, nor which repository is targeted.

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?

A single compact sentence with no filler, front-loading the operation and resource. The trailing "through optional authenticated gh CLI" is slightly compressed and ambiguous in its modifiers but carries useful information.

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

Completeness3/5

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

For a parameterless read-only tool with no output schema, the description covers the essential what and roughly how. It leaves notable gaps for an agent: implicit repo targeting, what metadata fields are returned, and failure behavior without gh or auth.

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?

There are zero parameters, which normally sets a baseline of 4, but the absence of any argument raises the critical implicit question of which repository is inspected (presumably the current working directory's remote) and the description never resolves it. The description therefore adds no semantic clarity about targeting.

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 ("Show GitHub repository metadata"), which is clearly distinct from issue/PR/git siblings by resource type. It stops short of explicitly contrasting itself with siblings like git_status or git_remote, which also surface repo-level information.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no named alternative. An agent cannot tell from this description whether to reach for github_repo_view, git_remote, or git_status when it wants repository information, and must infer usage from the name alone.

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