delete_repo
Permanently delete a repository by specifying its owner and name.
Instructions
Delete a repository by owner and name
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| owner | Yes | Owner/username | |
| repo | Yes | Repository name |
Permanently delete a repository by specifying its owner and name.
Delete a repository by owner and name
| Name | Required | Description | Default |
|---|---|---|---|
| owner | Yes | Owner/username | |
| repo | Yes | Repository name |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only says 'delete' but does not disclose irreversibility, permission requirements, or any side effects. Lacks critical behavioral info for a destructive operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single short sentence with no fluff. Could be slightly expanded for clarity but remains efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, no annotations, and description lacks details on return values, error states, or irreversible nature. Incomplete for a destructive tool with many siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for both parameters (owner, repo). Description adds no extra meaning beyond the schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the action (delete) and resource (repository) with identifying parameters (owner and name). It distinguishes from sibling tools like create_repo or edit_repo.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like transfer_repo. No context about prerequisites or scenarios where deletion is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sqcows/forgejo-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server