Forecall
Failure recordsDocs
All scored servers

2b2t Atlas: tool descriptions scored io.github.bobymicjohn/2b2t-atlas

tools/list taken
(UTC)
From
Official MCP Registry
Connected to
https://api.blackportal.cloud/mcp
Homepage
2b2tatlas.com/mcp/
Repository
github.com/bobymicjohn/2b2tAtlas-Public-API
Scoring rules
v2
Removal
support@forecall.dev
Score this URL as it is today

Scores, issues and names only

This page shows how 2b2t Atlas (io.github.bobymicjohn/2b2t-atlas)'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/io.github.bobymicjohn/2b2t-atlas
Average score
61.9 / 100Cloudy
Tools
38
Near-identical descriptions
1

Across the server

  • Minor
    38 tools. Above 25, models start to tell tools apart less well.many_tools

Tools whose descriptions are nearly the same

1 of 1 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
get_groupget_group_builds0.510.67

Tools

get_nocom_sign_history

41 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
3 / 25
Return value
8 / 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
  • Major
    Arguments without a description: id.param_no_description
  • Minor
    String arguments with no constraint or example: id.loose_string_param

find_nocom_daily_chunks

43 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
5 / 25
Return value
8 / 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
  • Major
    Arguments without a description: date, min_x, min_z, max_x, max_z, dimension, limit, cursor.param_no_description
  • Minor
    String arguments with no constraint or example: date.loose_string_param

find_nocom_rare_blocks

48 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
5 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Major
    Arguments without a description: dimension, kind, x, z, radius, min_y, max_y, limit, offset.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

get_nocom_daily_hits

48 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
5 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Major
    Arguments without a description: from, to, dimension, min_x, min_z, max_x, max_z.param_no_description
  • Minor
    String arguments with no constraint or example: from, to.loose_string_param

get_world_find_history

48 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
8 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: x, y, z, offset.param_no_description

search_nocom_signs

48 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
5 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Major
    Arguments without a description: text, x, z, dimension, radius, min_y, max_y, limit, offset.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

list_world_find_sources

49 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
14 / 25
Return value
8 / 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
  • Minor
    Arguments without a description: limit, offset.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

find_nocom_special_blocks

52 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
5 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: kind, dimension, x, z, radius, limit, offset.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

find_nocom_clusters

55 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
8 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Major
    Arguments without a description: x, z, dimension, radius, limit, offset.param_no_description

get_nocom_highway_activity

55 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
8 / 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
  • Minor
    No `required` list, so every argument is optional.no_required

get_nocom_periods

55 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
8 / 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
  • Minor
    No `required` list, so every argument is optional.no_required

find_nocom_storage

56 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
11 / 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
  • Major
    Arguments without a description: x, z, radius, min_y, max_y, hide_changed, limit, offset.param_no_description
  • Minor
    The meaning of the boolean argument hide_changed is unclear.vague_boolean

get_nocom_daily_dataset

57 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
25 / 25
Return value
8 / 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

get_nocom_dataset

57 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
25 / 25
Return value
8 / 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

find_nocom_portals

58 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
8 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Major
    Arguments without a description: x, z, dimension, radius, min_y, max_y, limit, offset.param_no_description

search_groups

62 / 100Cloudy

Purpose
17 / 20
When to use
10 / 20
Arguments
20 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description

search_highways

62 / 100Cloudy

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

search_nocom_sign_history

63 / 100Cloudy

Purpose
20 / 20
When to use
20 / 20
Arguments
5 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Major
    Arguments without a description: text, dimension, match, from, to, changed_only, min_x, min_z, max_x, max_z, sort, limit, offset.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument changed_only is unclear.vague_boolean

get_dataset_stats

64 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
25 / 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

get_world_find_inventory

64 / 100Cloudy

Purpose
20 / 20
When to use
10 / 20
Arguments
11 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Arguments without a description: observation_id, limit, offset, include_saved_data.param_no_description
  • Minor
    The meaning of the boolean argument include_saved_data is unclear.vague_boolean
  • Minor
    Required identifiers whose description does not say where the value comes from: observation_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

get_world_find_map

64 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
16 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Minor
    Arguments without a description: query, query.minZ, query.maxX, query.maxZ.param_no_description

find_preserved_builds

65 / 100Cloudy

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

get_group_builds

65 / 100Cloudy

Purpose
17 / 20
When to use
10 / 20
Arguments
23 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Its description is nearly the same as get_group's (similarity 0.51); only the names and schemas tell them apart. Say in this description when to use get_group instead.confusable_pair
  • Minor
    Required identifiers whose description does not say where the value comes from: group_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

research_location

67 / 100Cloudy

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

No issues.

find_locations_by_time_range

68 / 100Cloudy

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

No issues.

get_group

68 / 100Cloudy

Purpose
20 / 20
When to use
10 / 20
Arguments
23 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Its description is nearly the same as get_group_builds's (similarity 0.51); only the names and schemas tell them apart. Say in this description when to use get_group_builds instead.confusable_pair

get_highway

68 / 100Cloudy

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

No issues.

get_location

68 / 100Cloudy

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

No issues.

get_render_metadata

68 / 100Cloudy

Purpose
20 / 20
When to use
10 / 20
Arguments
23 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Required identifiers whose description does not say where the value comes from: location_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

find_recently_added_or_modified

70 / 100Clear

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

No issues.

research_area

70 / 100Clear

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

research_nocom_area

71 / 100Clear

Purpose
17 / 20
When to use
20 / 20
Arguments
7 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Arguments without a description: location_name, x, z, radius, location_id, include_storage, include_signs, include_portals, include_clusters.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument include_storage is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument include_signs is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument include_portals is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument include_clusters is unclear.vague_boolean

find_highways_near_location

73 / 100Clear

Purpose
20 / 20
When to use
10 / 20
Arguments
20 / 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

find_locations_near

73 / 100Clear

Purpose
20 / 20
When to use
10 / 20
Arguments
20 / 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

get_warps

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
  • Minor
    Required identifiers whose description does not say where the value comes from: location_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

search_locations

74 / 100Clear

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

get_world_downloads

80 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Required identifiers whose description does not say where the value comes from: location_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

search_world_find

82 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
17 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Minor
    Arguments without a description: query.minZ, query.maxX, query.maxZ.param_no_description
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description

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