Skip to main content
Glama

Geoa — Get found in ChatGPT

AI Visibility Report

geoa_ai_visibility
Read-onlyIdempotent

Your brand's AI visibility from geoa's stored scans: is your company mentioned when people ask ChatGPT, Claude, Gemini or Perplexity? Returns mention rate per engine, the top visibility gaps, and which competitors are cited instead. Reads stored scan results only (no live engine calls). Requires sign-in to a geoa account.

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": "geoa_ai_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world semantics, so the description is free to add real value — and it does, disclosing the data source (stored scans, no live engine calls) and the authentication requirement. It still leaves open what happens when no scans exist or how fresh the stored data is.

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?

Roughly fifty words in three sentences, with the core 'what you get' front-loaded and the constraints (stored-only, sign-in) trailing. The rhetorical question in the opening is slightly padded but does useful framing work; nothing is redundant.

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?

With no parameters and no output schema, the description must carry the return shape — and it names the three components (mention rate per engine, gaps, competitor citations). Missing only edge-case behavior (empty scan history, engine coverage limits) for a full picture.

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 tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to clarify. The description correctly implies no filtering inputs are accepted by describing a single aggregate report.

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?

States a specific resource (brand AI visibility from stored scans) and enumerates exactly what it returns: mention rate per engine, top visibility gaps, and which competitors are cited. The AI-engine-mention framing makes it clearly distinct from siblings like geoa_geo_score or geoa_radar_score_prospects without needing to name them.

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 by the scoping clauses 'from geoa's stored scans' and 'Reads stored scan results only (no live engine calls)', which tells the agent this is not a live query tool. However, it never explicitly says when to pick it over geoa_geo_score or the radar tools, and no preconditions beyond sign-in are given.

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