Skip to main content
Glama
Sign In
byline

byline

by indianic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Remove site

remove_site

Remove a publishing destination from the sites configuration file. Supply the site slug to delete that entry while leaving .env untouched.

Instructions

Remove a publishing target from config/sites.yaml. Leaves .env untouched.

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

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

A3.8/5.0
Behavior3/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. The statement 'Leaves .env untouched' provides useful scope, but it does not disclose other behaviors such as reversibility, error handling, or whether the operation is permanent. This is a moderate level of transparency.

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 concise sentences, front-loaded with the core action and followed by a useful caveat. Every word earns its place, with no redundancy or unnecessary detail.

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

Completeness3/5

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

The tool is simple with one parameter and no output schema, so the description is mostly adequate. It states the action and scope, but it fails to mention return values, error cases, or what happens if the slug doesn't exist. For a clean removal tool, it is acceptable but lacks some contextual completeness.

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 has one required parameter 'slug' with no description, and the tool description does not explain what slug refers to. Given 0% schema description coverage, the description should have clarified that slug is the identifier of the site to remove, but it does not, leaving the agent to infer meaning.

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 uses a specific verb 'Remove' and a clear resource 'publishing target from config/sites.yaml', which precisely defines the action. It also distinguishes itself from sibling tools like add_site and list_sites by focusing on the removal operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it by specifying the action and the target file (config/sites.yaml), giving clear context. However, it does not explicitly state when not to use it or list alternatives, so it doesn't fully meet the highest standard.

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