Skip to main content
Glama

Proximens Oracle

by io.github.cryptosun

Audit URL against Proximens GEO Engine

proximens_geo_audit_url
Read-only

Pro-tier. Fetch and analyze a web page, then audit it against the Proximens GEO Engine principles across all major GEO dimensions (structured data, crawler access, content depth, freshness, E-E-A-T, multimodal). INPUT: url (required, http/https); optional mode ("fast" = quick signal checks, returns in seconds — the default; "deep" = a full AI-synthesized consultancy report in Dutch with a 7-dimension scorecard and sector benchmark, takes ~30-50s), client_name (report header), branche_hint ("main:sub", e.g. "health_wellness:yoga_studio"), max_issues (1-25, default 10). RETURNS: JSON with a 0-100 score, severity-ranked issues (critical/major/minor) each with a finding and an actionable suggestion, top recommendations, and a markdown report; deep mode additionally returns score_set (7 GEO dimensions), sector (benchmark cohort), and a full consultancy-grade report_markdown (deep_mode="timeout_fallback" means the synthesis exceeded its budget and the fast result was returned instead). USE fast mode for quick checks and bulk triage; USE deep mode when you need a client-ready audit report. Free tier is blocked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesTarget URL to audit
modeNofast = quick signal checks (seconds); deep = full AI-synthesized consultancy report with sector benchmark (~30-50s)fast
max_issuesNoMaximum issues to return (default 10)
client_nameNoOptional client identifier for the audit report header
branche_hintNoBranche hint in "main:sub" format, e.g. "health_wellness:yoga_studio". If omitted, principles are matched without branche filter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_wmNo
urlYes
_metaNo
errorNo
scoreNo
sectorNoDetected sector benchmark cohort (deep mode only)
statusYes
signalsNo
audit_idYes
deep_modeNoDeep-mode outcome: ok = full synthesized report; timeout_fallback = synthesis exceeded budget, fast result returned
score_setNo7-dimension GEO scorecard (deep mode only)
recommendationsNo
report_markdownNo
matched_principlesNo

TDQS

A4.6/5.0
Behavior5/5

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

Adds significant context beyond annotations: describes fetch+analyze behavior, fast vs deep modes with timing, and deep mode timeout fallback. Annotations already signal read-only and open-world; description enriches with operational details.

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?

Well-structured with clear sectioning (INPUT, RETURNS, USE). Slightly verbose on deep mode fallback description, but overall efficient and front-loaded.

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?

Given output schema exists, description covers all necessary aspects: input format, mode options, return structure including fallback, and usage guidance. Complete for a tool of this complexity.

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?

Schema coverage is 100% lowering burden, but description adds value: explains mode trade-offs, branche_hint format and fallback, max_issues default. Goes beyond schema repetition.

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 the tool fetches and audits a web page against GEO engine principles. Distinguishes from siblings like bulk_search and compare_urls by focusing on single URL audit.

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?

Provides explicit guidance: 'USE fast mode for quick checks and bulk triage; USE deep mode when you need a client-ready audit report.' Notes free tier blocked. Does not explicitly mention when not to use, but context is clear.

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

All Proximens Oracle toolsInspect
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