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

content-engine-mcp

by DevMandalia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

search_seeds

Search seed titles, body text, and kinds by substring to find relevant content ideas or references in your local project.

Instructions

Substring search over seed title, body, and kind.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 behavioral burden. It discloses that matching is substring-based over title, body, and kind, but says nothing about case sensitivity, result limits, ordering, pagination, or permissions.

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?

A single compact sentence with zero wasted wording. The search behavior and target fields are front-loaded immediately.

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?

For a simple one-parameter search tool with no output schema, the description covers the core matching behavior. However, it omits return shape, ordering, limits, and when search is preferable to listing or direct retrieval.

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?

Schema description coverage is 0%, and the single query parameter is undocumented in the schema. The description partially compensates by explaining that the query is a substring matched against seed title, body, and kind, but it does not clarify matching rules such as case handling or multi-term behavior.

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?

States a specific verb and resource: substring search over seeds, and identifies the searched fields as title, body, and kind. It does not explicitly distinguish itself from siblings like list_seeds or get_seed, so it stops short of a 5.

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 search semantics imply it is used when looking for matching seeds, but there is no explicit guidance on when to use this instead of list_seeds or get_seed, nor any exclusion criteria. The agent must infer the alternative routing.

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