Skip to main content
Glama

Guidetopharmacology

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

A3.9/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds substantial value by detailing the output structure, the default free model, and the requirement for a user-provided API key for Anthropic, including cost responsibility. No contradictions with 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?

The description is two sentences plus a use-case line, with no wasted words. It front-loads the core action and output, then provides optional details and context. Extremely concise yet comprehensive.

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?

Given no output schema, the description adequately explains the return format (per-model score, confidence, signals, raw_response, plus combined view). It covers the 4 parameters well. However, it could clarify what 'signals' entails, but overall it is sufficient for an agent to understand the tool's inputs and outputs.

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 description coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by explaining the default model for the 'models' parameter, the purpose of '_apiKey', and how 'context' aids disambiguation. This enriches the agent's understanding.

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

Purpose4/5

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

The description clearly states the tool's function: probing LLMs for knowledge about an entity and returning a visibility score. It specifies the default model and optional Anthropic probing, aligning with the name. However, it does not explicitly differentiate from similar sibling tools like 'scan_competitor_ai_presence', which might cause confusion.

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

Usage Guidelines3/5

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

The description offers use cases like 'AI-marketing audits, pre-launch brand checks, competitive monitoring', providing context for when to use. However, it does not state when not to use or compare with alternative tools, leaving ambiguity about selection.

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

All Guidetopharmacology 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.6/5.0
Disambiguation2/5

Many tools have overlapping purposes, such as multiple ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) that differ only subtly, and a large set of prediction market tools (bet_research, polymarket_arbitrage, polymarket_edges, etc.) that can be easily confused. Entity tools like entity_profile, recent_changes, and compare_entities also overlap significantly. An agent would struggle to pick the right tool without careful reading.

Naming Consistency2/5

Tool names mix snake_case (ask_pipeworx, deep_research, forget) and descriptive phrases without a consistent verb_noun pattern. Some start with verbs (compare, generate, scan) while others are nouns or compound phrases (pipeworx_trending, polymarket_fill_risk). This inconsistency makes it hard to predict tool names.

Tool Count2/5

With 35 tools, this MCP server is overly large and covers many diverse domains (data querying, prediction markets, pharmacology, npm scanning, brand visibility, etc.). Typically, a well-scoped server has 5-15 tools; 35 is excessive and suggests a lack of focus, making it unwieldy for an agent to manage.

Completeness2/5

Despite the large number of tools, the server has notable gaps. For example, the pharmacology section only offers search and interaction tools but no create/update/delete. The memory tools are limited to save/recall/forget. Many meta-tools (discover_tools, suggest_questions) exist but add little substance. The server covers many domains superficially rather than providing full lifecycle coverage for any one domain.

Resources