This page shows how Boncourant (fr.boncourant/boncourant)'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/fr.boncourant/boncourant
Average score
45.2/ 100Cloudy
Tools
19
Near-identical descriptions
0
Across the server
No server-wide issues.
Tools
get_methodology
34/ 100Rain
Purpose
17 / 20
When to use
0 / 20
Arguments
2 / 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
Major
Arguments without a description: method_id, family, version.param_no_description
Minor
String arguments with no constraint or example: method_id, family, version.loose_string_param
Minor
No `required` list, so every argument is optional.no_required
run_method
39/ 100Rain
Purpose
17 / 20
When to use
0 / 20
Arguments
7 / 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
Major
Arguments without a description: method_id, version, valid_on, input, context, context.cta_fraction.param_no_description
Minor
String arguments with no constraint or example: method_id, version.loose_string_param
Minor
Required identifiers whose description does not say where the value comes from: method_id. Name the tool or the place that returns it, or models look it up first.id_source_missing
assess_historical_optimality
41/ 100Cloudy
Purpose
20 / 20
When to use
0 / 20
Arguments
6 / 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
String arguments with no constraint or example: customer.supportScheme, contracts[].reading_coverage.evidence[].title, contracts[].reading_coverage.evidence[].summary, contracts[].reading_coverage.evidence[].consequence, contracts[].reading_coverage.evidence[].excerpt, contracts[].reading_coverage.limitation.loose_string_param
Minor
The description mentions none of its 3 or more arguments.params_not_in_description
Minor
The meaning of the boolean argument customer.requested is unclear.vague_boolean
Minor
The meaning of the boolean argument customer.useUploadedProductionForPpa is unclear.vague_boolean
Minor
The meaning of the boolean argument customer.goRequired is unclear.vague_boolean
Minor
The meaning of the boolean argument customer.goTransferred is unclear.vague_boolean
Minor
The meaning of the boolean argument customer.alternatives[].comparable is unclear.vague_boolean
Minor
The meaning of the boolean argument customer.fixedPriceConfirmed is unclear.vague_boolean
Minor
The meaning of the boolean argument customer.costPerimeterComplete is unclear.vague_boolean
Minor
The meaning of the boolean argument customer.operationalReadinessConfirmed is unclear.vague_boolean
Minor
The meaning of the boolean argument customer.legalTaxReviewConfirmed is unclear.vague_boolean
Minor
The meaning of the boolean argument contracts[].reading_coverage.page_provenance_available is unclear.vague_boolean
extract_energy_document
47/ 100Cloudy
Purpose
17 / 20
When to use
0 / 20
Arguments
10 / 25
Return value
8 / 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
Major
Arguments without a description: document_kind, segment, evaluation_date, document_file, document_file.download_url, document_file.file_id, document_file.mime_type, document_file.file_name.param_no_description
Minor
String arguments with no constraint or example: document_file.download_url, document_file.file_id, document_file.mime_type, document_file.file_name.loose_string_param
Minor
The description mentions none of its 3 or more arguments.params_not_in_description
hc_schedule_change_impact
47/ 100Cloudy
Purpose
17 / 20
When to use
0 / 20
Arguments
10 / 25
Return value
8 / 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
The description mentions none of its 3 or more arguments.params_not_in_description
create_analysis_study
48/ 100Cloudy
Purpose
17 / 20
When to use
0 / 20
Arguments
13 / 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: target_tool, document_file.download_url, document_file.file_id, document_file.mime_type, document_file.file_name.param_no_description
Minor
String arguments with no constraint or example: document_file.download_url, document_file.file_id, document_file.mime_type, document_file.file_name.loose_string_param
Minor
The description mentions none of its 3 or more arguments.params_not_in_description
simulate
51/ 100Cloudy
Purpose
17 / 20
When to use
0 / 20
Arguments
19 / 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: option.param_no_description
Minor
String arguments with no constraint or example: postal_code.loose_string_param
eex_connector
52/ 100Cloudy
Purpose
17 / 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
analyze_bill
53/ 100Cloudy
Purpose
17 / 20
When to use
0 / 20
Arguments
21 / 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
String arguments with no constraint or example: postal_code, current_supplier.loose_string_param
pro_catalog
62/ 100Cloudy
Purpose
17 / 20
When to use
0 / 20
Arguments
25 / 25
Return value
8 / 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
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.