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

content-engine-mcp

by DevMandalia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_seed

Retrieve a single seed by seed_id to inspect the captured idea and its stored details before drafting content.

Instructions

Read one seed.

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": "get_seed"
  }
}

Input Schema

NameRequiredDescriptionDefault
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?

No annotations are supplied, so the description carries the full burden, yet it only implies a non-destructive read through the word "read." It says nothing about behavior when the seed_id does not exist, whether the response is cached, or what access is required.

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?

Three words with no filler and the resource is front-loaded, so there is nothing to trim, but the brevity reflects under-specification rather than efficient communication.

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?

A single-parameter read tool is simple, and there is no output schema to explain. Still, the definition never says what a seed is, what is returned, or how it differs from its many seed-related siblings, which is not enough for correct tool selection.

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 at 0% description coverage, and the description adds no meaning: it does not say seed_id is an identifier, what form it takes, or where to obtain one. The schema's bare {"type":"string"} is the only documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read one seed" gives a verb (read) and a resource (seed) with singular scope, which distinguishes it from list_seeds/search_seeds by implication only. It never states the retrieval key is seed_id, and the term "seed" is domain jargon left undefined.

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?

There is no guidance on when to fetch a single seed versus calling list_seeds or search_seeds, and no prerequisites or error conditions are mentioned. The agent must infer usage from the name alone.

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