com.dpf-it/mcp-server: tool descriptions scored

tools/list taken: 2026-11-02 (UTC)
From: Official MCP Registry
Connected to: https://api.dpf-it.com/mcp
Scoring rules: v2
Removal: support@forecall.dev

Scores, issues and names only

This page shows how com.dpf-it/mcp-server'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.dpf-it/mcp-server

Average score: 76.7 / 100Clear
Tools: 18
Near-identical descriptions: 0

Across the server

Minor
The server has no instructions. Say there, once, what the server is for and when to use it: Claude Code and Gemini CLI read the instructions before the tool descriptions.instructions_missing

Tools

delete_data_spec

41 / 100Cloudy

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

Major
The description only restates the name (9 words).restates_name
Major
Says nothing about when to use it, or when not to.no_usage_context

contact

48 / 100Cloudy

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

Major
Arguments without a description: reason, message, name.param_no_description
Minor
String arguments with no constraint or example: name.loose_string_param
Minor
Says nothing about what it returns.no_return_info

list_my_workspaces

60 / 100Cloudy

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

get_status

66 / 100Cloudy

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

create_workspace

67 / 100Cloudy

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

Minor
String arguments with no constraint or example: name, description.loose_string_param

finish_data_job

74 / 100Clear

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

No issues.

manage_account

74 / 100Clear

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

Minor
Arguments without a description: action, email.param_no_description
Minor
String arguments with no constraint or example: firstName, lastName.loose_string_param

run_data_job

79 / 100Clear

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

Minor
The description mentions none of its 3 or more arguments.params_not_in_description

setup_scheduled_pull

80 / 100Clear

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

No issues.

finish_data_source_onboarding

82 / 100Clear

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

No issues.

finish_data_spec_update

82 / 100Clear

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

No issues.

list_data

85 / 100Clear

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

No issues.

update_data_spec

85 / 100Clear

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

No issues.

manage_trigger

86 / 100Clear

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

No issues.

manage_connection

91 / 100Clear

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

No issues.

call_dpf_api

92 / 100Clear

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

No issues.

onboard_data_source

94 / 100Clear

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

Minor
The description is long (408 words). It helps selection but costs steps and tokens.too_long

submit_query

95 / 100Clear

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