All scored servers

DataPulse: tool descriptions scored io.github.r3dz4r/datapulse-my

tools/list taken
(UTC)
Connected to
https://mcp.data-pulse.my/mcp
Scoring rules
v2
Score this URL as it is today

Scores, issues and names only

This page shows how DataPulse (io.github.r3dz4r/datapulse-my)'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.r3dz4r/datapulse-my
Average score
96.0 / 100Clear
Tools
19
Near-identical descriptions
4

Across the server

Tools whose descriptions are nearly the same

4 of 4 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
find_anomaliesfind_deteriorating0.680.33
find_deterioratingfind_schema_drift0.670.25
find_deterioratingfind_recovering0.640.33
find_recoveringfind_schema_drift0.610.25

Tools

get_freshness_summary

90 / 100Clear

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

No issues.

check_reconciliation

95 / 100Clear

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

No issues.

find_anomalies

95 / 100Clear

Purpose
20 / 20
When to use
20 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Minor
    Its description is nearly the same as find_deteriorating's (similarity 0.68); only the names and schemas tell them apart. Say in this description when to use find_deteriorating instead.confusable_pair
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description

find_by_licence

95 / 100Clear

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

No issues.

find_deteriorating

95 / 100Clear

Purpose
20 / 20
When to use
20 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Minor
    Its description is nearly the same as find_anomalies's (similarity 0.68); only the names and schemas tell them apart. Say in this description when to use find_anomalies instead.confusable_pair
  • Minor
    Its description is nearly the same as find_schema_drift's (similarity 0.67); only the names and schemas tell them apart. Say in this description when to use find_schema_drift instead.confusable_pair
  • Minor
    Its description is nearly the same as find_recovering's (similarity 0.64); only the names and schemas tell them apart. Say in this description when to use find_recovering instead.confusable_pair

find_recovering

95 / 100Clear

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

find_schema_drift

95 / 100Clear

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

find_stale

95 / 100Clear

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

No issues.

find_unreliable

95 / 100Clear

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

No issues.

get_data_passport

95 / 100Clear

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

No issues.

get_dataset

95 / 100Clear

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

No issues.

get_evidence

95 / 100Clear

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

No issues.

verify_attestation

95 / 100Clear

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

No issues.

usage_summary

97 / 100Clear

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

No issues.

verify_dataset

97 / 100Clear

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

No issues.

get_provenance

100 / 100Clear

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

No issues.

search_datasets

100 / 100Clear

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

No issues.

trust_verdict

100 / 100Clear

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

No issues.

verify_evidence

100 / 100Clear

Purpose
20 / 20
When to use
20 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
10 / 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