This page shows how Atlasly (app.atlasly/atlasly)'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/app.atlasly/atlasly
Average score
64.2/ 100Cloudy
Tools
35
Near-identical descriptions
0
Across the server
Minor
35 tools. Above 25, models start to tell tools apart less well.many_tools
Major
34 tools repeat the same note (26 words). Say it once in the server's instructions, and let each description say what only that tool does. The note does not count toward the tools' scores.repeated_note
Minor
The server's instructions are 3937 characters. Claude Code reads only the first 2,048 by default (Codex 0.154.0 reads them whole). Put what the server is for first.instructions_long
Tools
view_geojson_file
46/ 100Cloudy
Purpose
20 / 20
When to use
0 / 20
Arguments
8 / 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: file, file.name, file.resourceUri.param_no_description
String arguments with no constraint or example: site_a.site_ref.version, site_a.site_ref.source_links[].label, site_b.site_ref.version, site_b.site_ref.source_links[].label, site_ref.version, site_ref.source_links[].label.loose_string_param
String arguments with no constraint or example: site_ref.version, site_ref.source_links[].label.loose_string_param
Minor
No `required` list, so every argument is optional.no_required
Minor
The meaning of the boolean argument include_calculators is unclear.vague_boolean
Minor
The meaning of the boolean argument include_standards is unclear.vague_boolean
Minor
The meaning of the boolean argument include_domains is unclear.vague_boolean
draft_site_description
74/ 100Clear
Purpose
17 / 20
When to use
20 / 20
Arguments
10 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
Major
Arguments without a description: site_ref.version, site_ref.status, site_ref.id, site_ref.canonical_address, site_ref.address_aliases, site_ref.coordinates, site_ref.boundary_id, site_ref.boundary_confidence, site_ref.jurisdiction, site_ref.country_code, site_ref.location_source, site_ref.local_planning_authority, site_ref.source_links, site_ref.source_links[].label, site_ref.source_links[].url, site_ref.project_id.param_no_description
Minor
String arguments with no constraint or example: site_ref.version, site_ref.source_links[].label.loose_string_param
check_permitted_development
76/ 100Clear
Purpose
17 / 20
When to use
15 / 20
Arguments
9 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
Major
Arguments without a description: site_ref.version, site_ref.status, site_ref.id, site_ref.canonical_address, site_ref.address_aliases, site_ref.coordinates, site_ref.boundary_id, site_ref.boundary_confidence, site_ref.jurisdiction, site_ref.country_code, site_ref.location_source, site_ref.local_planning_authority, site_ref.source_links, site_ref.source_links[].label, site_ref.source_links[].url, site_ref.project_id.param_no_description
Minor
String arguments with no constraint or example: site_ref.version, site_ref.source_links[].label.loose_string_param
site_verdict
76/ 100Clear
Purpose
17 / 20
When to use
15 / 20
Arguments
12 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
Major
Arguments without a description: site_ref.version, site_ref.status, site_ref.id, site_ref.canonical_address, site_ref.address_aliases, site_ref.coordinates, site_ref.boundary_id, site_ref.boundary_confidence, site_ref.jurisdiction, site_ref.country_code, site_ref.location_source, site_ref.local_planning_authority, site_ref.source_links, site_ref.source_links[].label, site_ref.source_links[].url, site_ref.project_id.param_no_description
Minor
String arguments with no constraint or example: site_ref.version, site_ref.source_links[].label.loose_string_param
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.