Skip to main content
Glama
dazeb

GitHub Mapper MCP Server

set-github-token

Configure a GitHub Personal Access Token for secure authentication to map and analyze GitHub repositories using the GitHub Mapper MCP Server.

Instructions

Set the GitHub Personal Access Token for authentication

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesGitHub Personal Access Token

Implementation Reference

  • The handler logic for the 'set-github-token' tool. It extracts the token from arguments, sets the global githubToken, initializes the Octokit client with authentication, and returns a success message.
    if (name === "set-github-token") {
      const { token } = args as { token: string };
      githubToken = token;
      octokit = new Octokit({ auth: githubToken });
      return {
        content: [
          {
            type: "text",
            text: "GitHub Personal Access Token has been set successfully.",
          },
        ],
      };
    } else if (name === "map-github-repo") {
  • src/index.ts:28-41 (registration)
    Registration of the 'set-github-token' tool in the ListToolsRequestHandler, providing name, description, and input schema.
    {
      name: "set-github-token",
      description: "Set the GitHub Personal Access Token for authentication",
      inputSchema: {
        type: "object",
        properties: {
          token: {
            type: "string",
            description: "GitHub Personal Access Token",
          },
        },
        required: ["token"],
      },
    },
  • Input schema definition for the 'set-github-token' tool, specifying the required 'token' string property.
    inputSchema: {
      type: "object",
      properties: {
        token: {
          type: "string",
          description: "GitHub Personal Access Token",
        },
      },
      required: ["token"],
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the authentication purpose without detailing behavioral traits. It doesn't disclose if this is a one-time setup, if it persists across sessions, what permissions the token needs, or potential side effects like overwriting existing tokens.

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 that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, 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?

For an authentication tool with no annotations and no output schema, the description is insufficient. It doesn't explain the authentication mechanism, how the token is stored/used, error handling, or what happens after setting the token, leaving critical context gaps.

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 the 'token' parameter fully. The description adds no additional meaning beyond what's in the schema, such as token format requirements or scopes needed, meeting the baseline for high coverage.

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 clearly states the action ('Set') and the resource ('GitHub Personal Access Token for authentication'), making the purpose immediately understandable. However, it doesn't differentiate from the sibling tool 'map-github-repo' or explain how this token setting relates to other GitHub operations, keeping it from a perfect score.

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, prerequisites, or context. It doesn't mention if this is for initial setup, token updates, or how it interacts with the sibling 'map-github-repo' tool, leaving usage unclear.

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

Related 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/dazeb/MCP-Github-Mapper'

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