Skip to main content
Glama
Sign In
content-engine-mcp

content-engine-mcp

by DevMandalia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

kill_seed

Removes a seed from the active content bank by seed ID, optionally recording a reason, so the idea is no longer available for drafting or scheduling.

Instructions

Kill a seed so it leaves the active bank.

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

Input Schema

NameRequiredDescriptionDefault
reasonNo
seed_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses that this is destructive and removes the seed from the active bank, but says nothing about reversibility, permissions, data retention, or the effect of the reason parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler. However, it is too terse for a mutation tool with two undocumented parameters and no annotations.

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?

This is a mutation tool with no annotations, no output schema, and zero parameter coverage, so the description needs to do much more. It states the core effect but omits reversibility, side effects, permissions, and parameter meaning.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for both parameters. It only vaguely refers to 'a seed' and never explains seed_id or what the reason parameter is for.

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?

'Kill a seed' names a specific verb and resource, and 'so it leaves the active bank' clarifies the resulting state. It is clearly a seed-level destructive operation, though it does not explicitly distinguish itself from siblings like revive_seed.

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 implies use when a seed should leave the active bank, but gives no explicit when-to-use guidance, prerequisites, or alternatives. It never mentions revive_seed or explains when killing is preferable to other seed operations.

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