iGods GEO Visibility Tool (GVT)

Set test visibility

gvt_set_test_visibility

Idempotent

Toggle the public visibility of a test session. Set is_public to true to make the test shareable and receive its public share URL, or false to make it private. The response confirms the new state and, when making a test public, includes the share_url the recipient can visit without any authentication. is_public is the only lever: true both publishes and yields the link in this same response; false revokes access to any previously issued share_url immediately. This is the only way to control who can view a test result without requiring MCP authentication.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tid`	Yes	The 8-character test ID returned by gvt_run_visibility_test.
`is_public`	Yes	true to make the test publicly shareable, false to make it private.

Output Schema

TableJSON Schema

Name	Required	Description
`tid`	No	The test that was modified
`success`	No	True when the visibility change was applied
`is_public`	No	The new public visibility state
`share_url`	No	Public share URL, present when is_public is true; the recipient needs no authentication. Null when sharing failed or the test is private

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

addedOutput schema / properties / share_url

Added value: +{
+  "description": "Public share URL, present when is_public is true; the recipient needs no authentication. Null when sharing failed or the test is private",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed3 schema fields changedSep 10, 2026
- addedOutput schema / properties / is_public / description
```
Added value: +"The new public visibility state"
```
- addedOutput schema / properties / success / description
```
Added value: +"True when the visibility change was applied"
```
- addedOutput schema / properties / tid / description
```
Added value: +"The test that was modified"
```

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "is_public": {
+      "type": "boolean"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "tid": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes well beyond the annotations, detailing response behavior (confirmation, share_url), authentication-free recipient access, immediate revocation of prior share URLs, and that is_public is the only control lever. This aligns with idempotentHint and destructiveHint and adds meaningful non-obvious behavior.

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 front-loaded with the core action, and every subsequent sentence contributes either behavioral nuance or usage context. There is no filler or repetition of what annotations already provide.

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?

With only two required parameters, a complete schema, and an output schema, the description covers all operational essentials: state change, response contents, share URL behavior, no-auth access, and revocation. No critical information is missing for correct invocation.

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%, so the baseline is 3. The description adds extra meaning by explaining the consequences of true vs false (publishing and returning share_url vs revoking access) and reinforcing that is_public is the only lever. tid's source is already fully documented in 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 opens with a specific action and resource: 'Toggle the public visibility of a test session.' It then explains the two states and their outcomes, and closes by positioning this as the only way to control who can view a test result, distinguishing it from the sibling list.

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?

It clearly states when to use the tool: when you want to share or privatize a test session ('This is the only way to control who can view a test result...'). It does not explicitly name sibling alternatives, but the 'only way' framing gives a strong selection signal.

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?