Skip to main content
Glama

Geoa — Get found in ChatGPT

GEO Score for Domain

geoa_geo_score
Read-onlyIdempotent

GEO score for a domain: how ready the site is to be read, understood and cited by AI search engines, measured across 15 technical dimensions. Returns the total score, a grade, and the 3 weakest dimensions (full 15-dimension report requires a geoa account). Results are cached for 6 hours per domain.

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": {
      "domain": "<domain>"
    },
    "name": "geoa_geo_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain, e.g. 'example.com'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: results are cached for 6 hours per domain, the response includes total score, grade and the 3 weakest dimensions, and the full 15-dimension report requires an account. That last point is important behavioral context an agent needs before promising a full report.

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?

Three sentences, front-loaded with the core purpose, then the return shape, then the caching caveat. No sentence is filler, and the key scoping constraint about the account is placed after the primary definition.

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?

There is no output schema, so the description must carry the return-value burden, and it does: total score, grade, and 3 weakest dimensions are named. The caching behavior and account limitation are also stated. It stops just short of describing the output structure fully (e.g., score range, grade scale), which keeps it from a 5.

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

Parameters3/5

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

There is only one parameter and the schema documents it fully at 100% coverage, including an example format. The description adds no format, validation, or edge-case guidance for the domain argument, which is acceptable given the schema baseline.

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 the specific resource (a domain) and the exact measurement: readiness to be read, understood and cited by AI search engines across 15 technical dimensions. It is concrete enough that an agent can distinguish it from sibling tools like geoa_ai_visibility or geoa_report_fixes_live without opening a schema.

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 description makes clear it's for scoring a domain's GEO readiness, but it gives no explicit when-to-use guidance, no alternatives, and no exclusions. An agent must infer that this is the entry point for domain-level analysis versus the account/visibility/fix tools.

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