Skip to main content
Glama
Sign In
agent-services-mcp

agent-services-mcp

by ludoplex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

git_import_repo

Import a GitHub repository by cloning it and optionally configuring a backup remote for redundancy.

Instructions

Clone an existing GitHub repository and configure backup remote. Saves ~470 tokens.

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": "<repo>"
    },
    "name": "git_import_repo"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoLocal path to clone to (optional)
repoYesRepository in format 'owner/repo'
withBackupNoCreate/configure backup remote (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only mentions cloning and configuring backup, but does not disclose authentication needs, potential overwrites, or error conditions.

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 two sentences, front-loaded with the main action, and contains no fluff. Every word is justified.

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 a tool that modifies the local filesystem, the description lacks information about output, error handling, and whether existing directories are replaced. The token savings note is a minor addition.

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 coverage is 100%, so the schema already documents all parameters. The description adds 'configure backup remote' which aligns with the withBackup parameter. No new parameter detail is added 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 clearly states 'Clone an existing GitHub repository and configure backup remote', which is a specific verb-resource-action pair. This distinguishes it from siblings like git_archive_repo (archive) and git_new_branch (branch).

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?

No explicit when-to-use or when-not-to-use guidance is provided. The description implies cloning an existing repo, but does not indicate alternatives or prerequisites.

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

Deploy Server

Other Tools