Skip to main content
Glama
Sign In
git-finder-mcp

git-finder-mcp

by dudckd6744
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remove_project

Remove a registered project from the searchable Git repos. Update your search scope by deleting projects you no longer need.

Instructions

등록된 프로젝트를 제거합니다.

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

Input Schema

NameRequiredDescriptionDefault
nameYes제거할 프로젝트 이름

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 carries the full burden of behavioral disclosure. The description only says 'removes' and does not clarify whether this is permanent, whether it deletes associated files, or what happens to the project's data. The word 'registered' provides a hint that it may only remove a registration, but this is not elaborated.

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, focused sentence that delivers the core purpose without any wasted words. It is front-loaded and easily scannable.

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 mutation tool with no annotations and no output schema, the description is too sparse. It does not mention side effects, error conditions, reversibility, or any safety context. The simplicity of the tool does not excuse the lack of behavioral detail.

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?

The schema includes a description for the single 'name' parameter, covering 100% of parameters. The tool description adds no additional meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 'Removes the registered project' clearly states the verb and resource, and it is distinct from sibling tools like add_project and list_projects. It immediately conveys what the tool does without ambiguity.

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?

The description implies the tool should be used when removing a project, but it provides no explicit guidance on when to use it versus other tools, nor does it mention prerequisites or alternative approaches. The purpose alone suggests the usage context.

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