Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

client_prompts

Manage a client workspace's prompt library: list saved prompts with visibility trends, add sweep prompts, and pause or resume prompts as needed.

Instructions

Manage a client workspace's prompt library: list saved prompts with per-prompt visibility trends, add a new sweep prompt, or pause/resume one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "client_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOptional tag applied when adding (e.g. 'pricing', 'comparison')
probeNoThe prompt text (required for add/toggle)
actionNolist (default) shows the library; add appends a prompt to the sweep set; toggle pauses/resumes one
domainNoAlternative lookup by client domain
enabledNoTarget state for toggle (default true = resume)
client_slugNoClient workspace slug (preferred lookup)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does correctly convey that add and toggle are mutating operations (appends, pauses/resumes) and that list is a read with per-prompt visibility trends, which is useful. It omits permissions/auth requirements, what happens when an already-existing prompt is added, whether toggling a nonexistent prompt fails, and what list actually returns, leaving meaningful behavioral gaps for a mutation-capable tool.

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 sentence with a front-loaded purpose clause followed by a colon and three parallel action clauses. Every clause maps to a distinct operation and there is no filler or repetition.

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 six-parameter, zero-required, mode-switching tool with no annotations and no output schema, the description covers the operation set adequately but leaves client identification (client_slug preferred vs domain alternative) and result content unexplained. The schema fills some of that gap, keeping this at a minimum-viable level rather than inadequate.

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% and every parameter carries its own explanation (tag, probe, action enum, domain, enabled, client_slug), so the schema does the heavy lifting and a baseline of 3 applies. The description adds only marginal meaning beyond that — the phrase "with per-prompt visibility trends" hints at list output, but nothing extra is said about the slug-vs-domain lookup choice or default 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?

The description gives a clear verb-plus-resource ("Manage a client workspace's prompt library") and then enumerates the three concrete operations: list with visibility trends, add a sweep prompt, pause/resume. An agent immediately knows what the tool does. It does not, however, differentiate itself from the sibling discover_prompts, so a reader cannot tell from this text alone why one would be chosen over the other.

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

Usage Guidelines3/5

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

The three actions are named, which implicitly signals usage, but there is no explicit when-to-use guidance, no prerequisite (e.g. that a client_slug or domain must be supplied), and no statement about when to prefer discover_prompts. The agent must infer the selection context from the action enum in the schema.

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