iGods GEO Visibility Tool (GVT)

Read GVT knowledge

gvt_get_knowledge

Read-onlyIdempotent

Read GVT reference knowledge: how scoring works, score bands and category weights, what each analysis category checks, or GEO glossary definitions. Use it to interpret test results and scores correctly instead of guessing. The topic is matched exactly and case-sensitively (Methodology will not match methodology); unrecognized values fail fast with the valid list. The same content is served as MCP resources at gvt://knowledge/app/* for resource-capable clients.

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

Input Schema

Name	Required	Description	Default
`topic`	No	Which knowledge topic to read: methodology (how GVT analyzes pages), scoring (score bands and category weights), categories (what each of the six categories checks), glossary (GEO term definitions), or all (complete knowledge base).	all

Output Schema

Name	Required	Description
`uri`	No	The gvt:// resource the content came from
`topic`	No	The topic that was served
`ttlMs`	No	Suggested client cache lifetime in milliseconds
`knowledge`	No	Reference content for the requested topic

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 10, 2026
- addedOutput schema / properties / topic / description
```
Added value: +"The topic that was served"
```
- addedOutput schema / properties / ttlMs / description
```
Added value: +"Suggested client cache lifetime in milliseconds"
```

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "knowledge": {
+      "description": "Reference content for the requested topic",
+      "type": "object"
+    },
+    "topic": {
+      "enum": [
+        "all",
+        "methodology",
+        "scoring",
+        "categories",
+        "glossary"
+      ],
+      "type": "string"
+    },
+    "ttlMs": {
+      "type": "integer"
+    },
+    "uri": {
+      "description": "The gvt:// resource the content came from",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds valuable behavioral detail: exact case-sensitive matching, failure behavior (fail fast with valid list), and the service as MCP resources. This provides extra context beyond 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?

Three sentences with no wasted words. The main purpose is front-loaded, followed by important matching details and resource alternative. Every sentence earns its place.

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?

The output schema exists, so return values are covered. The description covers purpose, usage, matching behavior, and failure handling. It's complete for a simple read-only knowledge tool with one optional parameter.

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?

The schema description covers 100% of parameters, so baseline 3 is appropriate. The description mentions exact matching and case-sensitivity, which reinforces the enum behavior, but doesn't add additional semantics beyond what the schema already explains.

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 tool reads GVT reference knowledge, listing specific content areas (scoring, bands, weights, categories, glossary). It distinguishes itself from sibling tools that run tests or get results, making selection unambiguous.

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?

The description gives clear context: use it to interpret test results instead of guessing. It doesn't explicitly name alternative tools, but given the tool's unique read-only knowledge role among siblings (e.g., gvt_get_test_results), the usage context is clear enough. Lacks explicit when-not conditions.

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?