Skip to main content
Glama
Sign In

MentionedOn Discovery Evidence Tools

by com.mentioned-on
OverviewDiscussionsAdmin

See visibility evidence and changes

get_visibility_report
Read-onlyIdempotent

Read a business's latest saved AI capture, competitors, source links and up to 30 prior snapshots. Compare scores only when saved model, prompt and capture recipes match and both captures are complete. Reports provider gaps and timestamps. This does not query models or establish current consumer-app inclusion.

Input Schema

NameRequiredDescriptionDefault
limitNo
businessIdYesBusiness id returned by list_monitored_businesses.

Output Schema

NameRequiredDescriptionDefault
latestYes
statusYes
byModelYes
historyYes
baselineYes
businessYes
evidenceYes
nextStepYes
reportUrlYes
competitorsYes
improvementYes
limitationsYes
scoreChangeYes
recommendationsYes
evidenceTruncatedYes
improvementHistoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / business / properties / monitoring
      Added value: +{
+  "enum": [
+    "live",
+    "paused",
+    "plan_limit",
+    "off",
+    "payment_failed"
+  ],
+  "type": "string"
+}
    • changedOutput schema / properties / business / required
      Previous value: -[
-  "id",
-  "name",
-  "website",
-  "active",
-  "onboardingStatus"
-]New value: +[
+  "id",
+  "name",
+  "website",
+  "active",
+  "monitoring",
+  "onboardingStatus"
+]
    • addedOutput schema / properties / nextStep
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / status / enum
      Previous value: -[
-  "ready",
-  "awaiting_baseline"
-]New value: +[
+  "ready",
+  "awaiting_baseline",
+  "awaiting_checkout",
+  "plan_required",
+  "payment_failed"
+]
    • changedOutput schema / required
      Previous value: -[
-  "business",
-  "status",
-  "latest",
-  "baseline",
-  "scoreChange",
-  "history",
-  "byModel",
-  "competitors",
-  "evidence",
-  "evidenceTruncated",
-  "recommendations",
-  "improvement",
-  "improvementHistory",
-  "reportUrl",
-  "limitations"
-]New value: +[
+  "business",
+  "status",
+  "nextStep",
+  "latest",
+  "baseline",
+  "scoreChange",
+  "history",
+  "byModel",
+  "competitors",
+  "evidence",
+  "evidenceTruncated",
+  "recommendations",
+  "improvement",
+  "improvementHistory",
+  "reportUrl",
+  "limitations"
+]
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

While annotations cover safety (`readOnlyHint: true`), the description adds vital context regarding the nature of the operation, specifying that it reads 'saved' snapshots rather than generating live data. This informs the agent about the temporal nature of the behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense, but every clause contributes to a functional definition. It is not overly verbose; it front-loads the key data points and behavioral constraints efficiently.

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?

Given that the tool performs a complex analysis of historical captures and comparisons, the description is highly complete. It covers the data sources, the comparison rules, and the operational limitations, leaving no ambiguity about its functionality.

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?

The description adds meaningful context to the 'limit' parameter by specifying that it controls the retrieval of 'prior snapshots,' which elevates the description beyond the basic schema definition. The definition for 'businessId' is also helpful.

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 is extremely specific, focusing on reading 'latest saved AI capture, competitors, source links and up to 30 prior snapshots.' It successfully differentiates this reporting function by stating it 'does not query models or establish current consumer-app inclusion'.

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

Usage Guidelines5/5

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

It provides explicit instructions on usage constraints, mandating that 'compare scores only when saved model, prompt and capture recipes match and both captures are complete.' It also provides a clear negative constraint, detailing what the tool does not do.

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

All MentionedOn Discovery Evidence Tools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Directories

Listed in ChatGPT · MentionedOn

Last observed

Resources