Skip to main content
Glama

MagicGEO — AI Search & Commerce Agent Seller

GEO fix recommendations

geo_recommendations
Read-onlyIdempotent

Return prioritized, actionable fixes that would make a public URL more citable by AI engines, with the recoverable score points, impact and effort for each fix.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic URL to analyze, e.g. https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety is covered; the description adds genuine behavioral context by disclosing the shape of the return payload (prioritized fixes with recoverable points, impact and effort). It does not mention limits such as analysis latency, failure modes for unreachable URLs, or how many fixes are returned, which keeps it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence that front-loads the outcome (fixes) before the payload details, with no filler or repetition. It is dense rather than bloated, though the trailing clause listing return fields is slightly comma-heavy to parse.

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 contract, and it does so reasonably by naming prioritized fixes plus impact/effort/point recovery. For a read-only, one-parameter tool with full annotation coverage this is close to sufficient; only sequencing relative to the audit step 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?

Schema coverage is 100% and the single parameter already documents itself as a 'Public URL to analyze, e.g. https://example.com'. The description restates the same 'public URL' constraint without adding format rules, validation behavior, or edge cases, so baseline 3 is appropriate.

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 a specific verb ('Return') and a concrete resource ('prioritized, actionable fixes') scoped to making a public URL more citable by AI engines, and it names the payload fields (recoverable score points, impact, effort). It stops short of distinguishing this from geo_audit, which by name likely produces the score these fixes attach to, so sibling differentiation is left implicit.

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 only implied: the mention of 'recoverable score points' hints this follows an audit, but the description never says when to call this versus geo_audit or geo_benchmark, nor any prerequisite such as needing a prior score. No exclusions or alternatives are named, so the agent must infer positioning from sibling names alone.

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