Skip to main content
Glama

Mediastack

by io.github.pipeworx-io

AI Visibility Check

ai_visibility_check
Read-onlyIdempotent

Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass _apiKey to also probe Anthropic (BYO key — you pay Anthropic directly for those calls). Returns per-model {score, confidence, signals, raw_response} + a combined view. Useful for AI-marketing audits, pre-launch brand checks, competitive monitoring.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityYesThe thing to ask about. Brand/business name, product name, person, or topic. E.g. "Pipeworx", "OpenInvoice", "Acme Corp pricing".
modelsNoWhich models to probe. Supported: "workers-ai" (free default), "anthropic" (requires _apiKey). Omit for just workers-ai.
_apiKeyNoOptional Anthropic API key (sk-ant-...) — only needed if "anthropic" is in models. Passed straight through to api.anthropic.com.
contextNoOptional: a phrase locating the entity (e.g. "Boston restaurant", "B2B SaaS"). Helps disambiguate common names.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate read-only, idlempotent, and non-destructive nature. The description adds valuable behavioral details: default free model, BYO key for Anthropic with direct billing, and return format. No contradiction.

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?

The description is a single, well-structured paragraph that front-loads key information (purpose, default model, optional behavior). Every sentence adds value; no wasted words.

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

Completeness5/5

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

For a tool with 4 parameters, no output schema, and rich annotations, the description fully explains return format (per-model object + combined), use cases, optional parameters, and model costs. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds meaning beyond names/descriptions: default model behavior, API key pass-through, and context disambiguation. This justifies a score above baseline 3.

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 the tool's purpose: probing LLMs for knowledge about an entity and scoring visibility. It uses specific verbs like 'probe' and 'score', specifies the default model, and differentiates from siblings like 'scan_competitor_ai_presence'.

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?

The description provides use cases (AI-marketing audits, brand checks, monitoring) and explains how to use the tool with default or Anthropic models. It lacks explicit when-not-to-use guidance but offers clear context and optional parameters.

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

All Mediastack 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

A4.1/5.0
Disambiguation5/5

Each tool has a detailed description clarifying its precise purpose, and even closely related tools (e.g., ask_pipeworx vs ask_pipeworx_grounded) are clearly differentiated by behavior and use case. No two tools appear to serve the same function.

Naming Consistency3/5

All names use snake_case, but the structural pattern is inconsistent: many follow verb_noun (compare_entities, resolve_entity), while others are noun-based (entity_profile, polymarket_arbitrage) or single verbs (subscribe, remember). This mix reduces predictability.

Tool Count3/5

With 32 tools, the server is quite large for an MCP server. While many tools are justified by the broad domain coverage, the high number can overwhelm agents and increase cognitive load, making it feel somewhat bloated.

Completeness4/5

The tool set covers a wide range of domains (company data, prediction markets, news, memory, subscriptions, etc.), and the generic ask_pipeworx and deep_research tools gateways to thousands of data sources, effectively filling gaps. However, some areas lack dedicated tools (e.g., weather, real estate) beyond the generic query.

Resources