iGods GEO Visibility Tool (GVT)

Get latest snapshot

gvt_get_latest

Read-onlyIdempotent

Get the most recent non-expired test snapshot for a single URL. For pre-computed baseline-vs-latest deltas without fetching full snapshots, use gvt_get_score_trend instead. Use with gvt_get_baseline to compare baseline vs current when you need the full snapshot detail on both ends. The url must be passed exactly as the test was run — matching is exact string equality, not nearest-match; an unrecorded URL returns 404. Considers only the authenticated caller's own non-expired tests.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	The URL to look up (must match the URL used when the test was run).

Output Schema

Name	Required	Description
`tid`	No	Test ID of the snapshot
`url`	No	The URL this snapshot analyzed
`latest`	No	Null when no test exists for the URL
`status`	No	Snapshot status (completed, failed, etc.)
`message`	No	Present only in the no-test case
`isPublic`	No	Whether this test is publicly visible
`testType`	No	The type of the test run
`createdAt`	No	ISO 8601 instant this snapshot was created
`expiresAt`	No	ISO 8601 instant this snapshot will expire
`updatedAt`	No	ISO 8601 instant this snapshot was last updated
`shareableTid`	No	Public share ID, non-null when shareable
`analysisSummary`	No	Aggregate scores for this test
`findingSentence`	No	Pre-generated natural language verdict for this snapshot

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedSep 10, 2026
- changedOutput schema / properties / analysisSummary / description
```
Previous value: -"Aggregate scores for one test session"New value: +"Aggregate scores for this test"
```
- changedOutput schema / properties / analysisSummary / properties / categoryIssueCounts / properties / accessibility / description
```
Previous value: -"Accessibility score (0-100)"New value: +"Number of open accessibility issues"
```
- changedOutput schema / properties / analysisSummary / properties / categoryIssueCounts / properties / accessibility / type
```
Previous value: -"number"New value: +"integer"
```
- changedOutput schema / properties / analysisSummary / properties / categoryIssueCounts / properties / headings / description
```
Previous value: -"Heading structure score (0-100)"New value: +"Number of open heading structure issues"
```
- changedOutput schema / properties / analysisSummary / properties / categoryIssueCounts / properties / headings / type
```
Previous value: -"number"New value: +"integer"
```
- changedOutput schema / properties / analysisSummary / properties / categoryIssueCounts / properties / javascript / description
```
Previous value: -"JavaScript dependency score (0-100)"New value: +"Number of open JavaScript dependency issues"
```
- changedOutput schema / properties / analysisSummary / properties / categoryIssueCounts / properties / javascript / type
```
Previous value: -"number"New value: +"integer"
```
- changedOutput schema / properties / analysisSummary / properties / categoryIssueCounts / properties / nojs / description
```
Previous value: -"No-JS rendering score (0-100)"New value: +"Number of open No-JS rendering issues"
```
- changedOutput schema / properties / analysisSummary / properties / categoryIssueCounts / properties / nojs / type
```
Previous value: -"number"New value: +"integer"
```
- changedOutput schema / properties / analysisSummary / properties / categoryIssueCounts / properties / schema / description
```
Previous value: -"schema.org markup score (0-100)"New value: +"Number of open schema.org markup issues"
```
- changedOutput schema / properties / analysisSummary / properties / categoryIssueCounts / properties / schema / type
```
Previous value: -"number"New value: +"integer"
```
- changedOutput schema / properties / analysisSummary / properties / categoryIssueCounts / properties / semantic / description
```
Previous value: -"Semantic HTML5 score (0-100)"New value: +"Number of open semantic HTML5 issues"
```
- changedOutput schema / properties / analysisSummary / properties / categoryIssueCounts / properties / semantic / type
```
Previous value: -"number"New value: +"integer"
```
- changedOutput schema / properties / analysisSummary / properties / categoryIssueCounts / properties / social / description
```
Previous value: -"Social tags score (0-100)"New value: +"Number of open social tag issues"
```
- changedOutput schema / properties / analysisSummary / properties / categoryIssueCounts / properties / social / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / expiresAt
```
Added value: +{
+  "description": "ISO 8601 instant this snapshot will expire",
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / isPublic
```
Added value: +{
+  "description": "Whether this test is publicly visible",
+  "type": "boolean"
+}
```
- addedOutput schema / properties / testType
```
Added value: +{
+  "description": "The type of the test run",
+  "enum": [
+    "url",
+    "html_paste"
+  ],
+  "type": "string"
+}
```
- addedOutput schema / properties / updatedAt
```
Added value: +{
+  "description": "ISO 8601 instant this snapshot was last updated",
+  "type": "string"
+}
```
Changed10 schema fields changedSep 10, 2026
- addedOutput schema / properties / analysisSummary / properties / categoryIssueCounts / description
```
Added value: +"Open issue count per analysis category"
```
- addedOutput schema / properties / analysisSummary / properties / categoryScores / description
```
Added value: +"Score per analysis category (0-100)"
```
- addedOutput schema / properties / analysisSummary / properties / jsDependencySource / description
```
Added value: +"How the JS dependency score was derived"
```
- addedOutput schema / properties / createdAt / description
```
Added value: +"ISO 8601 instant this snapshot was created"
```
- addedOutput schema / properties / findingSentence / description
```
Added value: +"Pre-generated natural language verdict for this snapshot"
```
- addedOutput schema / properties / message / description
```
Added value: +"Present only in the no-test case"
```
- addedOutput schema / properties / shareableTid / description
```
Added value: +"Public share ID, non-null when shareable"
```
- addedOutput schema / properties / status / description
```
Added value: +"Snapshot status (completed, failed, etc.)"
```
- addedOutput schema / properties / tid / description
```
Added value: +"Test ID of the snapshot"
```
- addedOutput schema / properties / url / description
```
Added value: +"The URL this snapshot analyzed"
```

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Most recent non-expired snapshot for one URL. On success the snapshot fields sit at the top level; when no test exists the response is { url, latest: null, message }.",
+  "properties": {
+    "analysisSummary": {
+      "description": "Aggregate scores for one test session",
+      "properties": {
+        "categoryIssueCounts": {
+          "properties": {
+            "accessibility": {
+              "description": "Accessibility score (0-100)",
+              "type": "number"
+            },
+            "headings": {
+              "description": "Heading structure score (0-100)",
+              "type": "number"
+            },
+            "javascript": {
+              "description": "JavaScript dependency score (0-100)",
+              "type": "number"
+            },
+            "nojs": {
+              "description": "No-JS rendering score (0-100)",
+              "type": "number"
+            },
+            "schema": {
+              "description": "schema.org markup score (0-100)",
+              "type": "number"
+            },
+            "semantic": {
+              "description": "Semantic HTML5 score (0-100)",
+              "type": "number"
+            },
+            "social": {
+              "description": "Social tags score (0-100)",
+              "type": "number"
+            }
+          },
+          "type": "object"
+        },
+        "categoryScores": {
+          "properties": {
+            "accessibility": {
+              "description": "Accessibility score (0-100)",
+              "type": "number"
+            },
+            "headings": {
+              "description": "Heading structure score (0-100)",
+              "type": "number"
+            },
+            "javascript": {
+              "description": "JavaScript dependency score (0-100)",
+              "type": "number"
+            },
+            "nojs": {
+              "description": "No-JS rendering score (0-100)",
+              "type": "number"
+            },
+            "schema": {
+              "description": "schema.org markup score (0-100)",
+              "type": "number"
+            },
+            "semantic": {
+              "description": "Semantic HTML5 score (0-100)",
+              "type": "number"
+            },
+            "social": {
+              "description": "Social tags score (0-100)",
+              "type": "number"
+            }
+          },
+          "type": "object"
+        },
+        "jsDependencySource": {
+          "enum": [
+            "measured",
+            "estimated",
+            "unavailable"
+          ],
+          "type": "string"
+        },
+        "overallScore": {
+          "description": "Overall GEO visibility score (0-100)",
+          "type": "number"
+        },
+        "timestamp": {
+          "description": "ISO 8601 instant of the analysis",
+          "type": "string"
+        },
+        "totalIssues": {
+          "description": "Total open issues across all categories",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "createdAt": {
+      "type": "string"
+    },
+    "findingSentence": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "latest": {
+      "description": "Null when no test exists for the URL",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "message": {
+      "type": "string"
+    },
+    "shareableTid": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "type": "string"
+    },
+    "tid": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 9, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds valuable specifics: exact string equality matching (not nearest-match), 404 on unrecorded URL, and scoping to the caller's own non-expired tests. While it doesn't detail response contents, the output schema exists to cover that. It goes beyond the annotations without contradicting them.

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?

The description is concise—four sentences, each serving a purpose: primary function, alternative tool, combination usage, and matching constraint. Information is front-loaded, and there is no redundant phrasing.

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 single-parameter read-only tool with a full output schema and safety annotations, the description covers all necessary operational details: what it returns (latest non-expired snapshot), how to invoke it correctly (exact URL match), what errors to expect (404), and scope (own tests). No critical gap remains.

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% (the url parameter description matches the intent), and the description adds the exact-match requirement and 404 behavior, which the schema does not specify. It also clarifies the operation is for a single URL. This adds meaningful context beyond the schema.

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?

The description clearly states the operation: 'Get the most recent non-expired test snapshot for a single URL.' It distinguishes itself from the sibling gvt_get_score_trend by noting that tool is for pre-computed deltas, and also references gvt_get_baseline for full snapshot comparison. This is a specific verb+resource with explicit sibling differentiation.

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 names when to use gvt_get_score_trend instead ('For pre-computed baseline-vs-latest deltas without fetching full snapshots') and when to combine with gvt_get_baseline ('when you need the full snapshot detail on both ends'). It also provides a critical constraint: URL must match exactly, with 404 on mismatch. This gives clear, actionable selection guidance.

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

All iGods GEO Visibility Tool (GVT) tools Inspect

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

Need Help?