Skip to main content
Glama
apexseo-geo-mcp

apexseo-geo-mcp

Live x402 USDC Pricing & Tool Menu

geo_pricing
Read-onlyIdempotent

Fetch the free pricing manifest for ApexSEO GEO audit endpoints, covering Base USDC prices, endpoint paths, and MCP connection details. Use it before paid calls to confirm costs and routing.

Instructions

Free pricing manifest listing all ApexSEO GEO audit endpoints, Base Mainnet (eip155:8453) USDC prices ($0.01-$0.05), endpoint paths, and MCP Streamable HTTP connection details. Ideal sibling to geo_health before dispatching paid calls.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
payToYes
networkYes
currencyYes
endpointsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description's real contribution is the 'free' qualifier (no USDC is charged to read it) and the chain identifier for the quoted prices, which is genuinely useful context for a payment-adjacent tool. It does not clarify caching/freshness of the quoted prices, which matters when an agent is about to spend money based on them.

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, front-loaded with the resource and its contents before the usage hint, with no filler. The closing clause ('Ideal sibling to geo_health...') is slightly promotional in tone but carries actionable routing information, so it still earns its place.

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?

An output schema exists, so the description is not obligated to describe the return shape, and it correctly focuses on what the manifest contains. For a zero-parameter, read-only tool this is nearly sufficient; the only missing element an agent would want is whether the listed prices are stable or time-sensitive.

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, so the baseline is 4 and there is no semantic gap to compensate for. The description does not waste words inventing parameter behavior, which is correct here.

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 names a specific resource (a free pricing manifest) and enumerates its contents: GEO audit endpoints, Base Mainnet (eip155:8453) USDC prices in a $0.01-$0.05 range, endpoint paths, and Streamable HTTP connection details. That is far more specific than the title alone, though differentiation from the five audit siblings rests on a single relational clause rather than an explicit contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear call-site: use it as a sibling to geo_health before dispatching paid calls, which tells the agent this is a discovery/setup step rather than an audit action. It stops short of stating exclusions, e.g. that it should not be used to actually run or price a single specific audit, so it falls one step below fully explicit when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.