Skip to main content
Glama

Data Brussels

by io.github.pipeworx-io

Scan Competitor AI Presence

scan_competitor_ai_presence
Read-onlyIdempotent

Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our competitors?". Returns ranked list with score, confidence, signal density per entity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelsNoWhich models to probe. Supported: "workers-ai" (free default), "anthropic" (requires _apiKey). Omit for just workers-ai.
_apiKeyNoOptional Anthropic API key — only if "anthropic" is in models. Passed to api.anthropic.com per probe.
contextNoOptional shared context applied to every probe (e.g. "B2B SaaS", "Boston restaurant"). Disambiguates common names.
entitiesYesArray of 2-8 entities to compare (brand/business/product names). First entry treated as the "subject" for narrative; rest are competitors.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds that it probes each entity, ranks by score, and returns a ranked list with score, confidence, signal density—valuable context beyond annotations.

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 plus an example and return description. Front-loaded with main purpose, no wasted words.

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?

Completeness is high: explains tool function, how it works internally, and return format. Could be slightly more explicit about entity count constraint (2-8) but overall sufficient.

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 coverage is 100% with parameter descriptions. The description adds the narrative that the first entity is the 'subject' for narrative, but does not add significant meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it compares AI visibility across multiple entities side-by-side, ranks them, and surfaces the most/least recognized. It distinguishes from sibling tool 'ai_visibility_check' by specifying multi-entity comparison.

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

Usage Guidelines4/5

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

Explicitly states usefulness for competitive AI-marketing audits with an example question, implying when to use. Does not explicitly mention alternatives like using ai_visibility_check repeatedly, but context makes it clear.

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

All Data Brussels toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes, with clear descriptions differentiating similar ones like ask_pipeworx and ask_pipeworx_grounded. However, some overlap exists between deep_research and ask_pipeworx, though descriptions provide guidance.

Naming Consistency2/5

Tool names are inconsistent, mixing snake_case (ai_visibility_check), multi-word phrases (scan_competitor_ai_presence), and simple verbs (query, recall). No uniform pattern like verb_noun convention.

Tool Count3/5

33 tools is on the high side, but the server covers a broad domain (data querying, prediction markets, subscriptions). It feels slightly heavy but still manageable; borderline between reasonable and excessive.

Completeness3/5

The Pipeworx and prediction market tools are comprehensive, but Brussels Open Data is underrepresented with only three tools (query, dataset_info, search_datasets). Missing update/delete operations for Brussels data, though likely read-only.

Resources