Skip to main content
Glama

Monarch Initiative

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. Changed4 schema fields changed
    • addedInput schema / properties / _apiKey
      Added value: +{
+  "description": "Optional Anthropic API key (sk-ant-...) — only needed if \"anthropic\" is in models. Passed straight through to api.anthropic.com.",
+  "type": "string"
+}
    • changedInput schema / properties / context / description
      Previous value: -"Optional: a phrase locating the entity (e.g. \"Boston restaurant\", \"B2B SaaS\", \"Polish painter\"). Helps disambiguate common names."New value: +"Optional: a phrase locating the entity (e.g. \"Boston restaurant\", \"B2B SaaS\"). Helps disambiguate common names."
    • changedInput schema / properties / entity / description
      Previous value: -"The thing to ask about. Brand/business name, product name, person, or topic. E.g. \"Pipeworx\", \"OpenInvoice\", \"Acme Corp pricing\", \"the company behind ChatGPT\"."New value: +"The thing to ask about. Brand/business name, product name, person, or topic. E.g. \"Pipeworx\", \"OpenInvoice\", \"Acme Corp pricing\"."
    • addedInput schema / properties / models
      Added value: +{
+  "description": "Which models to probe. Supported: \"workers-ai\" (free default), \"anthropic\" (requires _apiKey). Omit for just workers-ai.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses that the tool makes external API calls, the default model is free, and using Anthropic requires a BYO API key with direct cost to the user. This adds valuable behavioral context about cost and external dependencies.

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 three sentences, each serving a distinct purpose: what it does, how to invoke extended functionality, and when to use it. There is no redundancy or filler, making it both concise and information-dense.

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?

With no output schema, the description compensates by specifying the return structure (per-model {score, confidence, signals, raw_response} + combined view). It also covers input semantics, model options, cost, and practical use cases, making it complete for a tool of this complexity.

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?

The input schema already provides 100% coverage with descriptions for all four parameters (entity, models, _apiKey, context). The tool description adds the default model and cost context, but these are also implied in the schema's model descriptions. The description does not add significant new semantics 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 identifies the tool's action ('Probe one or more LLMs'), the resource (business/brand/product/topic), and the output (visibility score 0-100 per model). It differentiates from siblings like scan_competitor_ai_presence by focusing on per-model scoring and a combined view.

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 explicit use cases ('AI-marketing audits, pre-launch brand checks, competitive monitoring') and explains how to invoke specific models (default Workers AI, optional Anthropic with _apiKey). It does not mention when not to use it or compare directly with sibling tools, so it stops short of a 5.

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

All Monarch Initiative 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.7/5.0
Disambiguation4/5

Most tools have clear, distinct purposes, especially within the same domain (e.g., Polymarket betting tools each serve a specific function). However, the multiple data-querying tools (ask_pipeworx, ask_pipeworx_grounded, deep_research) could cause confusion despite detailed descriptions.

Naming Consistency3/5

Many tools follow a verb_noun snake_case pattern (e.g., bet_research, compare_entities), but there are exceptions like ai_visibility_check, forget, and suggest_questions. The mix of imperative verbs and descriptive phrases creates inconsistency.

Tool Count2/5

With 35 tools, the server feels overloaded. While each domain (biomedical, financial, betting) is covered extensively, the sheer number of tools likely overwhelms agents, and many tools could be merged or split into separate servers.

Completeness4/5

The tool set is comprehensive for its declared purpose, covering biomedical queries, company data, betting analysis, memory management, and more. Minor gaps exist (e.g., no tool to delete a bet, no write operations for biomedical data), but the breadth is impressive.

Resources