iGods GEO Visibility Tool (GVT)

Delete a test

gvt_delete_test

DestructiveIdempotent

Permanently delete a test session and all its associated results. This action cannot be undone. Use gvt_set_test_visibility instead if you only want to hide a test from public view. Deleting a test does not delete its schedule (if one exists): recurring runs continue until removed via gvt_schedule_test delete mode.

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": {
      "tid": "<tid>"
    },
    "name": "gvt_delete_test"
  }
}

Input Schema

Name	Required	Description	Default
`tid`	Yes	The 8-character test ID of the test to delete.

Output Schema

Name	Required	Description	Default
`message`	No	Human-readable confirmation
`success`	No	True when the test was deleted

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 10, 2026
- addedOutput schema / properties / message / description
```
Added value: +"Human-readable confirmation"
```
- addedOutput schema / properties / success / description
```
Added value: +"True when the test was deleted"
```

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

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

First observedSep 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already indicate destructive and non-read-only behavior, but the description adds significant context: the action cannot be undone, associated results are deleted, and existing schedules are preserved. These are non-obvious behaviors that the agent cannot infer from the schema or annotations.

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 first sentence states the core action and scope, the second flags permanence, and the third covers both the alternative and the schedule caveat. 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 description is complete for a destructive single-parameter tool. It covers the action, side effects, reversibility, and alternative routing. An output schema exists, so explaining return values is unnecessary, and the annotation profile already covers safety semantics.

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 single parameter 'tid' is already fully documented in the schema as 'The 8-character test ID of the test to delete.' The description does not add further meaning about the parameter beyond what the schema provides, so the baseline score applies.

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 a specific action, resource, and scope: 'Permanently delete a test session and all its associated results.' It explicitly distinguishes itself from the sibling gvt_set_test_visibility, leaving no ambiguity about what this tool does.

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?

The description says exactly when to choose an alternative: 'Use gvt_set_test_visibility instead if you only want to hide a test from public view.' It also clarifies the boundary with scheduled tests, telling agents that recurring runs continue unless removed via gvt_schedule_test delete mode.

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?