Forecall
Failure recordsDocs
All scored servers

iGods GEO Visibility Tool (GVT): tool descriptions scored com.igods/gvt

tools/list taken
(UTC)
From
Official MCP Registry
Connected to
https://mcp.geo.igods.com/mcp
Homepage
geo.igods.com
Repository
github.com/CameronKnowlton/gvt-mcp
Scoring rules
v2
Removal
support@forecall.dev
Score this URL as it is today

Scores, issues and names only

This page shows how iGods GEO Visibility Tool (GVT) (com.igods/gvt)'s tool descriptions scored, the issues found and the names of its tools and parameters. The descriptions are the server's own: read them where the copy came from.

Forecall asked the URL this server lists in the official MCP Registry for its tools/list once, on the date above, without calling any tool. The server may have changed since.

servers/com.igods/gvt
Average score
72.2 / 100Clear
Tools
19
Near-identical descriptions
0

Across the server

No server-wide issues.

Tools

gvt_get_score_trend

60 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    No `required` list, so every argument is optional.no_required

gvt_list_sitemap_urls

61 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
21 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

gvt_delete_test

63 / 100Cloudy

Purpose
17 / 20
When to use
10 / 20
Arguments
18 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
0 / 10

No issues.

gvt_list_baselines

65 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

gvt_run_visibility_test

65 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
18 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

gvt_list_prompts

68 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
0 / 10

No issues.

gvt_set_test_visibility

68 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
18 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
0 / 10

No issues.

gvt_get_fix

70 / 100Clear

Purpose
20 / 20
When to use
5 / 20
Arguments
18 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10

No issues.

gvt_get_prompt

70 / 100Clear

Purpose
20 / 20
When to use
5 / 20
Arguments
18 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10

No issues.

gvt_list_schedules

71 / 100Clear

Purpose
17 / 20
When to use
10 / 20
Arguments
19 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Minor
    No `required` list, so every argument is optional.no_required

gvt_get_baseline

73 / 100Clear

Purpose
20 / 20
When to use
20 / 20
Arguments
18 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10

No issues.

gvt_get_knowledge

73 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
23 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10

No issues.

gvt_get_batch_summary

78 / 100Clear

Purpose
20 / 20
When to use
10 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
0 / 10

No issues.

gvt_run_visibility_batch

78 / 100Clear

Purpose
17 / 20
When to use
20 / 20
Arguments
16 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Minor
    Arguments without a description: urls[].addToSchedule.param_no_description

gvt_schedule_test

79 / 100Clear

Purpose
17 / 20
When to use
15 / 20
Arguments
19 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
  • Minor
    Arguments without a description: urls[].addToSchedule.param_no_description

gvt_get_batch_status

80 / 100Clear

Purpose
17 / 20
When to use
15 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
0 / 10

No issues.

gvt_list_tests

80 / 100Clear

Purpose
20 / 20
When to use
20 / 20
Arguments
17 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Minor
    No `required` list, so every argument is optional.no_required

gvt_get_latest

83 / 100Clear

Purpose
20 / 20
When to use
20 / 20
Arguments
18 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
0 / 10

No issues.

gvt_get_test_results

87 / 100Clear

Purpose
20 / 20
When to use
20 / 20
Arguments
20 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10

No issues.

What static scoring cannot tell

This score reads only the text of each description and schema: it says what is written, not what a model will do. Short tools whose names already say what they do, such as browser_close, score low here even when models use them well, and in our measurements current models chose the right tool in one step even from one-line descriptions, as long as the names and schemas differed. What the text cannot show, such as what happens over several steps and whether an added sentence helps or misleads, is what an evaluation measures, on the Pro and Team plans.

Is your server listed here and you would rather it were not? Email support@forecall.dev, and we will take it off within 7 days.

All scored servers