Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

get_repository_info

Retrieve GitHub repository details including owner and repository information through the Multi-MCPs server's unified API integration.

Instructions

Get GitHub repository details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYes
repoYes

Implementation Reference

  • The handler function for get_repository_info tool. Validates GitHub token and inputs, then calls client.getRepository.
    async get_repository_info(args: Record<string, unknown>) {
      if (!cfg.githubToken) throw new Error("GITHUB_TOKEN is not configured");
      const owner = String(args.owner || "");
      const repo = String(args.repo || "");
      if (!owner || !repo) throw new Error("owner and repo are required");
      return client.getRepository(owner, repo);
    },
  • Input schema for the get_repository_info tool defining required 'owner' and 'repo' string parameters.
    inputSchema: {
      type: "object",
      properties: {
        owner: { type: "string" },
        repo: { type: "string" },
      },
      required: ["owner", "repo"],
    },
  • Registration of the get_repository_info tool in the registerGitHub function, including name, description, and schema.
    {
      name: "get_repository_info",
      description: "Get GitHub repository details",
      inputSchema: {
        type: "object",
        properties: {
          owner: { type: "string" },
          repo: { type: "string" },
        },
        required: ["owner", "repo"],
      },
    },
  • Helper method in GitHubClient class that performs the actual API request to fetch repository information.
    getRepository(owner: string, repo: string) {
      return this.request(`/repos/${owner}/${repo}`);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Get' implies a read operation but doesn't specify whether this requires authentication, rate limits, what details are returned, or error handling. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence with zero wasted words. It's appropriately sized for a simple tool and front-loaded with the core purpose, making it easy to parse quickly.

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

Completeness2/5

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

Given the tool has 2 parameters with 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain what details are returned, how to handle errors, or usage constraints, leaving the agent with insufficient information to use the tool effectively.

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

Parameters2/5

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

The schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'GitHub repository details' but doesn't explain what 'owner' and 'repo' parameters represent, their expected formats, or examples. This fails to add meaningful semantics beyond the bare schema.

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 'Get GitHub repository details' clearly states the action ('Get') and resource ('GitHub repository details'), making the tool's purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'search_repositories' which might serve a similar domain, missing explicit differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives like 'search_repositories' or other GitHub-related tools. It lacks context about prerequisites, such as needing specific repository access, or when this tool is preferred over searching for repositories.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TaylorChen/muti-mcps'

If you have feedback or need assistance with the MCP directory API, please join our Discord server