Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

discover_prompts

Find high-intent buyer prompts across commercial evaluation, comparison, technical architecture, and pricing ROI, then apply Princeton KDD lift tactics to improve AI search visibility.

Instructions

Discover high-intent buyer prompts across 4 strategic pillars (commercial evaluation, head-to-head comparison, technical architecture, pricing ROI) with Princeton KDD lift tactics.

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": {
      "brand": "<brand>",
      "domain": "<domain>"
    },
    "name": "discover_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYesBrand or product name (e.g. 'Supabase', 'Linear')
nicheNoOptional category or problem domain
domainYesCanonical website domain (e.g. 'supabase.com')
competitorsNoOptional list of competitor names to include in comparison queries

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 behavioral burden and does not meet it. It never says whether prompts are generated at request time or retrieved from storage, whether the call is expensive or slow, what the response contains, or what 'Princeton KDD lift tactics' actually means as behavior; the jargon obscures rather than discloses.

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

Conciseness4/5

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

A single front-loaded sentence with the key object and the pillar enumeration up front, with no redundant restatement. It loses a point for dense unexplained jargon ('Princeton KDD lift tactics') that consumes space without adding actionable meaning.

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 4-parameter, 2-required tool with no annotations and no output schema, the definition covers the input side adequately via the schema but leaves the return shape and the generation-vs-lookup nature unexplained. An agent can plausibly invoke it, but cannot predict cost, latency, or output structure.

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 100%, with all four parameters documented inline including examples ('supabase.com', optional competitors list), so the schema does the work and a baseline of 3 applies. The description adds no parameter-level meaning beyond it, such as how competitors change the comparison-pillar output or how niche filters results.

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?

The description names a specific verb ('Discover') and resource ('high-intent buyer prompts'), then enumerates the four content pillars, so an agent knows it produces categorized buyer-intent queries for a brand. It does not, however, distinguish itself from the sibling tool 'client_prompts', which plausibly touches similar territory.

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 statement of when to call this versus the siblings, no prerequisites, and no exclusions. The only context is implicit in the phrase 'high-intent buyer prompts', which suggests a GEO/content-planning workflow but never says so, leaving the agent to guess how it differs from client_prompts or the visibility tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.