Skip to main content
Glama

MentionedOn Visibility and Website Fixes

Summarize AI Scan Evidence

summarize_scan_evidence
Read-only

Use when you captured AI answers yourself: calculates how often the business is mentioned and how often its own site is cited, overall and per assistant, with the statements that support each number. Free; it does not call AI providers, fetch URLs or store anything, and it says nothing beyond the answers supplied.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "businessName": "<businessName>",
      "observations": "<observations>"
    },
    "name": "summarize_scan_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
businessNameYes
observationsYesPoint-in-time captures supplied by the caller. The tool will not obtain new captures.

Output Schema

NameRequiredDescriptionDefault
scopeYes
bySourceYes
limitationsYes
unavailableYes
businessNameYes
mentionCountYes
completedCountYes
observedAtRangeYes
observationCountYes
unavailableCountYes
evidenceStatementsYes
mentionRatePercentYes
sentimentBreakdownYes
businessCitationCountYes
establishesLiveInclusionYes
businessCitationRatePercentYes
uniqueBusinessCitationHostsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/destructive annotations, it discloses that the tool is free, makes no AI provider calls, fetches no URLs, stores nothing, and reports nothing beyond the supplied answers. That is real behavioral context an agent needs for cost and side-effect reasoning, not a restatement of annotations.

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?

Two sentences, front-loaded with the trigger condition, and every clause carries information (scope, cost, side effects, data limits). The semicolon chains make it dense and slightly harder to scan than it needs to be.

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?

An output schema exists, so return values need no explanation, and the annotations cover safety. The description closes the remaining gaps an agent needs: input provenance, absence of external calls, no persistence, and the strict input-derived scope of results.

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?

With 50% schema description coverage, the description contributes meaning by framing observations as point-in-time caller-supplied captures that will not be supplemented or refetched, and by implying 'per assistant' grouping via source labels. It does not explain the completed-vs-error/skipped item variants or the citation URL field, which remain schema-only.

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 names a specific computation (mention frequency and own-site citation frequency, overall and per assistant) plus the supporting statements behind each number. The opening clause 'Use when you captured AI answers yourself' distinguishes it from siblings like get_ai_referrals that obtain data rather than summarizing caller-supplied captures.

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?

It gives a clear triggering condition: use it when you captured AI answers yourself, which implicitly excludes scenarios where new captures are needed. It stops short of naming an alternative tool for the case where the caller has no captures, so the exclusion is inferred rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources