codeglance-mcp

by lucidopus

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_repository_info

Check if a GitHub repository is cloned locally and retrieve its metadata, including analysis suitability.

Instructions

Get information about a repository and whether it's already cloned locally.

Args:
    repo_url: GitHub repository URL
    working_directory: Directory where analysis folder should be located

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": {
      "repo_url": "<repo_url>"
    },
    "name": "get_repository_info"
  }
}

Input Schema

Name	Required	Description	Default
`repo_url`	Yes
`working_directory`	No		.

Output Schema

Name	Required	Description
`repo_url`	Yes	GitHub repository URL
`repo_name`	Yes	Repository name
`local_path`	Yes	Local path where repository would be/is stored
`already_cloned`	Yes	Whether repository is already cloned locally
`working_directory`	Yes	Working directory used

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3May 26, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that it checks local clone status, implying filesystem access, but does not specify network requirements, authorization, or other behaviors. It adds some context but lacks completeness.

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 concise with a clear first sentence stating purpose, followed by parameter descriptions. No unnecessary words or 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?

Given the tool's simplicity (2 parameters, no nested objects, output schema exists), the description adequately covers purpose and parameter meanings. However, it lacks usage guidelines and behavioral details that would be helpful for an agent, but it's not severely incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It adds meaningful descriptions: 'GitHub repository URL' for repo_url and 'Directory where analysis folder should be located' for working_directory, which go beyond the schema's just names and types.

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 clearly states 'Get information about a repository and whether it's already cloned locally', providing a specific verb and resource. It distinguishes this from sibling tools like 'analyze_repository' which likely performs analysis, and 'list_generated_guides' which lists guides.

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?

No explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, limitations, or when not to use it. Given the existence of sibling tools, this is a significant gap.

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

Deploy Server