Skip to main content
Glama

SurfacedBy AI Visibility & GEO Audit

See where AI platforms get their answers

surfacedby_get_ai_source_landscape
Read-onlyIdempotent

For each AI platform, the mix of source types it cites, recent changes in which sources it cites, and how its answers cite, from SurfacedBy's published AI Search Index, with the data date, the public page and related research with links. Figures are pooled across many brands: they describe each platform, not any one business.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "surfacedby_get_ai_source_landscape"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNo
platformNo

Output Schema

NameRequiredDescriptionDefault
statusYes
platformsNo
next_stepsNo
source_urlYes
limitationsNo
window_daysNo
data_throughNo
evidence_kindNopublished_ai_source_landscape
corpus_answersNo
corpus_citationsNo
research_findingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish this as a read-only, idempotent, non-destructive, open-world fetch, so the description does not need to cover safety. It instead adds genuinely useful behavior beyond the annotations: the data provenance (published AI Search Index), that a data date accompanies results, that public page and related-research links are included, and the important limitation that figures are pooled across brands rather than describing one business.

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, no filler, with the scope caveat placed last as a qualifier. The first sentence is a long list-heavy run-on and the phrase 'how its answers cite' is vague, which slightly hurts readability, but no sentence is wasted.

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

Completeness3/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 not be explained, and annotations cover the safety profile. What is missing is any guidance on the two optional filters and no routing to sibling tools for brand-specific or per-page evidence questions, which leaves meaningful gaps for an agent choosing among the four siblings.

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

Parameters2/5

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

Schema description coverage is 0% and the description never mentions either parameter. The 21-value 'topic' enum and 7-value 'platform' enum are only self-describing value lists in the schema, with no explanation of what a topic filter means, whether the two filters combine, or what omitting them returns. The description does not compensate for the coverage gap at all.

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 states precisely what the tool returns: per-platform source-type mix, recent citation changes, and citation behavior, drawn from SurfacedBy's AI Search Index. It also distinguishes itself from brand-level siblings by declaring the figures are pooled across many brands, so an agent can tell it is not a per-business lookup. The only weakness is the absence of an explicit verb up front, since it describes the payload rather than saying 'Retrieve the source landscape'.

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?

Usage is implied rather than stated: the tool is for platform-level questions about where AI answers come from, and the pooled-figures caveat signals it is the wrong tool for brand-specific questions. No sibling is named as an alternative and there are no explicit when-to-use or when-not-to-use rules.

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.