Skip to main content
Glama

audit_geo_lite

Read-onlyIdempotent

FREE lite GEO readiness audit of a brand/storefront URL. Runs the same 20 checks as audit_geo but returns top-line results only: 0-100 score, A-F grade, check counts, and the titles of the top gaps — no per-check evidence, no detailed recommendations. Use this to triage whether a site needs the full audit_geo report, or call audit_geo directly for the complete evidence-backed audit.

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": {
      "url": "<url>"
    },
    "name": "audit_geo_lite"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesBrand/storefront URL to audit, e.g. https://example-brand.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the lower bar applies. The description still adds real behavioral context beyond them: it discloses that the same 20 checks run underneath, that outputs are deliberately truncated ('no per-check evidence, no detailed recommendations'), and that it is free — useful cost/scope signals. It stops short of stating rate limits or latency, which keeps it from a 5.

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?

Two sentences, front-loaded with the free/lite framing and the scorecard contents, then the routing decision. Every clause carries information — the negative clauses about missing evidence are the most decision-relevant part, not filler.

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?

There is no output schema, so the description must describe the return shape, and it does: 0-100 score, A-F grade, check counts, and top gap titles, plus what is explicitly excluded. For a one-parameter read-only tool, nothing an agent needs to call it or interpret results correctly is missing.

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 a single parameter with 100% schema description coverage, so the schema already documents the URL argument and its format. The description only loosely reinforces this with 'brand/storefront URL', adding marginal meaning. Baseline 3 is appropriate.

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 verb and resource ('GEO readiness audit of a brand/storefront URL') and immediately scopes it as the lite variant that runs the same 20 checks as audit_geo but returns top-line results only. This makes it distinguishable from the sibling audit_geo without opening either schema.

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 states the explicit selection rule: use this to triage whether a site needs the full report, or call audit_geo directly for the complete evidence-backed audit. Both the when-to-use and the when-to-use-the-alternative conditions 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