Proximens Oracle

Compare URLs against Proximens GEO Engine

proximens_geo_compare_urls

Read-only

Pro-tier. Fetch two web pages (your URL and a competitor's) and audit both against the Proximens GEO Engine principles using the same audit engine as audit_url, then compute the delta. INPUT: self_url and competitor_url (both required, http/https). RETURNS: JSON with a 0-100 score per URL (same scoring as audit_url), the principles each page satisfies, the principles each page VIOLATES that the other satisfies (delta_principles), and strategic insights on where to close the gap. USE WHEN you want a competitive GEO gap analysis between your page and a rival's.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`self_url`	Yes	Your URL to audit
`competitor_url`	Yes	Competitor URL to compare against

Output Schema

TableJSON Schema

Name	Required	Description	Default
`_meta`	No
`error`	No
`insights`	Yes
`self_url`	Yes
`self_score`	Yes
`self_matched`	Yes
`competitor_url`	Yes
`competitor_score`	Yes
`delta_principles`	Yes
`competitor_matched`	Yes

TDQS

A5/5.0

Behavior5/5

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

Discloses return format (JSON with scores, principles, violations, insights) and that it uses the same engine as audit_url. No contradiction with annotations (readOnlyHint, openWorldHint).

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 plus structured INPUT/RETURNS section. No wasted words, front-loaded with purpose and key details.

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?

Tool has only two simple parameters and output schema exists (referenced). Description covers usage, inputs, outputs, and differentiators. Fully adequate.

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

Parameters5/5

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

Both parameters have descriptions in schema, and description adds value by noting both are required and http/https format. Schema coverage is 100%.

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?

Clearly states it compares two URLs against GEO Engine principles, differentiates from sibling audit_url. Specific verb 'compare' and resource 'URLs' with clear scope.

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?

Explicitly says 'USE WHEN you want a competitive GEO gap analysis' and contrasts with audit_url. Provides clear context for when to choose this tool.

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

All Proximens Oracle tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool targets a distinct operation: auditing a URL, comparing two URLs, bulk search, single principle lookup, stats, category listing, semantic search, and brief synthesis. Even audit_url and compare_urls are clearly separated by the comparison/delta aspect.

Naming Consistency5/5

All tools follow a consistent proximens_geo_ prefix with snake_case and mostly verb_noun pattern (audit_url, compare_urls, get_principle, get_stats, list_categories, search_principles, synthesize_brief). bulk_search is a minor variation but still fits the readable convention.

Tool Count5/5

8 tools is well-scoped for a specialized GEO engine API. Each tool covers a clear need without redundancy, and the count is neither too thin nor overwhelming.

Completeness4/5

The surface covers the main workflows: discovering principles (search, categories, stats), retrieving details (get_principle), auditing URLs (audit, compare), bulk operations (bulk_search), and generating briefs. A minor gap is lack of a direct 'list all principles by category' endpoint, but search with category filter effectively covers this.

Resources

Need Help?