optifeed-radar
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_API_KEY | No | Google API key for Gemini engine | |
| OPENAI_API_KEY | No | OpenAI API key for ChatGPT engine | |
| ANTHROPIC_API_KEY | No | Anthropic API key for Claude engine | |
| PERPLEXITY_API_KEY | No | Perplexity API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_visibilityA | Ask real AI engines real buyer questions and score whether this brand gets recommended. Use when you want the AI Visibility Score for a domain. COST: spends real API money (roughly $0.05-$0.30/run depending on engines and prompt count); capped at $0.50 by default - pass max_cost to change it. |
| audit_store | Zero-key, zero-cost readiness audit: robots.txt AI-bot access, llms.txt, structured data, meta, sitemap. Use for a fast free check with no API keys. COST: free (no LLM calls). |
| generate_buyer_queriesA | Generate the buyer questions this brand should be visible for (discovers the brand profile first, then writes a query pack). Use to preview or seed the prompts before a paid check_visibility run. COST: a small number of judge calls for discovery + generation (typically under $0.05). |
| shopping_checkA | Check whether AI engines recommend specific PRODUCTS you name (beta). Returns each product scored 0-100 on whether engines recommend it, sorted with the ones they never named first, plus the rival products filling the shelf instead. Use for SKU-level questions; use check_visibility for the brand as a whole. There is no product discovery, so the list must be supplied. COST: spends real API money and is larger than a brand check. Each product costs about 4 prompts on every engine with a key, which extrapolates from measured check runs to roughly $0.20 per product across four engines; capped at $0.20 per product by default - pass max_cost to change it. |
| get_snapshot_diffA | Compare the two most recent check_visibility runs for a domain (score and per-engine deltas). Use to see what changed between runs. COST: free (reads saved snapshots). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct aspect: brand-level visibility, query generation, product-level check, and run comparison. No overlap in purposes.
Most names follow verb_noun pattern (check_visibility, generate_buyer_queries, get_snapshot_diff), but 'shopping_check' is a noun_noun compound, creating a slight inconsistency.
4 tools cover the core functionality without being excessive or insufficient. The scope is well-calibrated for the domain.
Core operations are present, but missing a tool to list past runs or view a single run's details, which could be useful for auditing.