Skip to main content
Glama

Innovalyxx Sovereign Edge

by io.github.dcvalentino69-ux
OverviewDiscussionsAdmin

Agent / site visibility snapshot

get_agent_visibility
Read-onlyIdempotent

Returns a 0–100 generative-engine visibility score and estimated LLM mention rate for a URL. Cost $0.01 per call. Not HTTP uptime, TLS, or a credit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAbsolute HTTPS URL whose generative-engine visibility score and estimated LLM mention rate should be returned.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNoTrue when the tool completed without a validation error.
urlNoQueried URL.
toolNoTool name that produced this payload.
paymentNoSettlement receipt after x402 or sandbox payment.
geo_scoreNo0–100 generative-engine visibility score.
estimated_llm_mention_rateNoEstimated LLM mention rate for the URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / url / description
      Previous value: -"Absolute HTTPS URL to check for HTTP status, TLS validity, response time, and site score."New value: +"Absolute HTTPS URL whose generative-engine visibility score and estimated LLM mention rate should be returned."
    • changedOutput schema / description
      Previous value: -"URL health / site-score snapshot (HTTP, TLS, response time, 0-100 score)."New value: +"Generative-engine visibility snapshot (geo_score and estimated_llm_mention_rate)."
    • changedOutput schema / properties / estimated_llm_mention_rate / description
      Previous value: -"Deterministic mention-rate estimate."New value: +"Estimated LLM mention rate for the URL."
    • changedOutput schema / properties / geo_score / description
      Previous value: -"0-100 site score from HTTP + local weights."New value: +"0–100 generative-engine visibility score."
  2. Changed3 schema fields changed
    • changedInput schema / properties / url / description
      Previous value: -"Merchant URL whose estimated LLM mention rate and GEO score should be returned."New value: +"Absolute HTTPS URL to check for HTTP status, TLS validity, response time, and site score."
    • changedOutput schema / description
      Previous value: -"Estimated agent-visibility metrics for a URL."New value: +"URL health / site-score snapshot (HTTP, TLS, response time, 0-100 score)."
    • changedOutput schema / properties / geo_score / description
      Previous value: -"Latest stored GEO score, if any."New value: +"0-100 site score from HTTP + local weights."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds valuable context beyond that: the $0.01 per-call cost and the explicit statement of what the metric is not. This is useful behavioral disclosure for an agent deciding whether to invoke the tool.

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?

Three short sentences, each earning its place: the return value, the cost, and the negative scope. Information is front-loaded and free of 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?

For a one-parameter read-only tool with an output schema present, this description covers what the call returns, the cost, and its boundaries. Nothing essential is missing for an agent to select and invoke it correctly.

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%, so the schema already fully documents the single `url` parameter. The description adds minimal parameter meaning beyond restating that the score applies 'for a URL', which is consistent but not additive. 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?

States a specific verb ('Returns') with a clear resource (generative-engine visibility score and LLM mention rate for a URL), and directly distinguishes itself from HTTP/TLS/credit checks. An agent can immediately understand the tool's core function.

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 clear exclusions ('Not HTTP uptime, TLS, or a credit'), helping an agent know when NOT to use this tool. It doesn't explicitly name a sibling alternative, but the negative scope meaningfully guides selection among the listed verify/agent tools.

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

All Innovalyxx Sovereign Edge toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources