w0-mcp-server
Server Details
Look up a brand's AI Recommendation Rate: how often it's the #1 AI pick.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP ยท MCP 2025-06-18
- URL
- Repository
- modern-ai-inc/w0-mcp-server
- GitHub Stars
- 0
- Server Listing
- w0-mcp-server
TDQS
Scored across 1 tool
There is only one tool, so no ambiguity or overlap exists. Its purpose is clearly described as looking up a brand's AI Recommendation Rate and Inclusion Rate. Agents cannot confuse it with any other tool.
The single tool name follows a clean snake_case verb_noun pattern and is descriptive. However, with only one tool, there is insufficient evidence to confirm a consistent naming convention across a tool set, so a perfect score is not given.
At one tool, the server is on the thin end of the scale. For a narrowly scoped free lookup endpoint it is acceptable, but it feels minimal compared to typical multi-tool MCP servers. A couple of related lookup or comparison tools would make the count more robust.
The tool fully delivers its stated purpose by returning both the AI Recommendation Rate and Inclusion Rate for a single brand. It lacks multi-brand or historical lookup options, but those are outside the explicit 'single-brand lookup only' scope, so the gap is minor.
Available Tools
1 toollookup_brand_recommendation_rateAInspect
Look up a brand's AI Recommendation Rate: the percentage of buyer-intent questions where the brand is the #1 AI pick (not just mentioned), plus its Recommendation Inclusion Rate (appears anywhere in the answer). Free, single-brand lookup only -- rate-limited per Modern AI's published anti-scrape policy.
| Name | Required | Description | Default |
|---|---|---|---|
| brand | Yes | Brand name to look up, e.g. "Brumate" |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that the operation is a rate-limited, single-brand lookup, which is meaningful behavioral context beyond the schema. It does not cover auth or error behavior, but the essential characteristics are clearly stated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences front-load the purpose and distinguish the two metrics. Every clause adds value, including the single-brand and rate-limit caveats, with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter lookup with no output schema, the description specifies exactly what is returned (the two rates) and the constraints on invocation. Nothing an agent needs to decide whether to call it or interpret the result is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already documents the brand parameter at 100% coverage, including an example. The description adds no parameter-specific detail beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Look up') and resource (brand's AI Recommendation Rate), with precise definitions of the two metrics returned. The description makes the tool's function unambiguous and distinguishes it from mere mention counting.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit constraints: free, single-brand lookup only, and rate-limited per anti-scrape policy. It does not name alternatives, but with no siblings this is sufficient context for when the tool should be used.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
lookup_brand_recommendation_rate
Related MCP Connectors
Free, no signup. Check if ChatGPT, Perplexity & Google AI recommend a brand in 15 markets (GEO/AEO).
Measure whether AI assistants actually recommend a brand, from measured answers.
Measure whether AI assistants actually recommend a brand, from measured answers.
Query your brand's AI visibility across ChatGPT, Claude, Perplexity, and Gemini.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables measuring whether AI assistants actually recommend a brand when buyers ask for a recommendation, returning visibility check results as three-band verdicts and counts.21 npm1MIT
- AlicenseAqualityCmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.169 npm1MIT

prompteye-mcpofficial
AlicenseAqualityAmaintenanceEnables querying a brand's visibility in AI assistant answers, including competitor presence, tracked prompts, and the answers and sources behind the metrics.20MIT- AlicenseAqualityCmaintenanceEnables AI visibility analysis for brands, providing scores, sentiment, competitor comparison, and recommendations across multiple AI models like Claude and GPT-4o.215 npm1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.