Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

client_snapshot

Pull the stored AI-visibility analytics snapshot for one CiteContext client workspace: visibility history, per-engine breakdown, per-prompt trends, and current action plan from recorded sweep data.

Instructions

Pull the stored AI-visibility analytics snapshot for one CiteContext client workspace: visibility history, per-engine breakdown, per-prompt trends, and the current action plan. Reads only recorded sweep data — nothing is estimated.

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_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoAlternative lookup by client domain (e.g., 'acme.com')
client_slugNoClient workspace slug (e.g., 'acme'). Preferred lookup.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/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 burden, and it does disclose the read-only, non-computational nature ('Reads only recorded sweep data — nothing is estimated'), which is genuinely useful. It omits auth/permission needs, behavior when no sweep data exists, and whether results are paginated or truncated.

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?

Two sentences, zero filler, with the core action and payload front-loaded before the read-only caveat. Nothing needs trimming.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by enumerating the returned sections, which is what an agent most needs. Remaining gaps are secondary: the domain-vs-slug resolution order and empty-state behavior.

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 already documents both domain and client_slug, including which is preferred. The description adds only the 'one client workspace' scoping constraint and gives no guidance on what happens if both parameters are supplied simultaneously.

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 ('Pull the stored AI-visibility analytics snapshot') and enumerates the payload (visibility history, per-engine breakdown, per-prompt trends, action plan). The 'stored snapshot' framing implicitly separates it from live-query siblings such as get_ai_search_visibility, but no sibling is named explicitly.

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?

Implies usage via 'for one CiteContext client workspace' and 'Reads only recorded sweep data', which signals retrieval of already-recorded results rather than running a new sweep. It never states when to prefer this over get_ai_search_visibility or geo_audit_domain, nor any preconditions such as requiring prior sweeps to exist.

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