Forecall
Failure recordsDocs
All scored servers

FieldPulse MCP by usefulapi: tool descriptions scored io.usefulapi/fieldpulse

tools/list taken
(UTC)
From
Official MCP Registry
Connected to
https://fieldpulse.usefulapi.io/mcp
Homepage
usefulapi.io/fieldpulse/
Repository
github.com/m190/usefulapi-mcp
Scoring rules
v2
Removal
support@forecall.dev
Score this URL as it is today

Scores, issues and names only

This page shows how FieldPulse MCP by usefulapi (io.usefulapi/fieldpulse)'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.usefulapi/fieldpulse
Average score
38.5 / 100Rain
Tools
43
Near-identical descriptions
2

Across the server

  • Major
    43 tools. Above 40, models choose less accurately.too_many_tools

Tools whose descriptions are nearly the same

2 of 2 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
fieldpulse_list_customer_contactsfieldpulse_get_customer_contact0.600.33
fieldpulse_get_customerfieldpulse_get_customer_contact0.500.75

Tools

fieldpulse_list_tags

28 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (8 words).restates_name
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: object_type.param_no_description
  • 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
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_projects

30 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
17 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (8 words).restates_name
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: sort_by.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_asset_categories

33 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (5 words).restates_name
  • Major
    The description is too short (5 words).too_short
  • 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
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_contracts

33 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (6 words).restates_name
  • Major
    The description is too short (6 words).too_short
  • 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
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_lead_sources

33 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (6 words).restates_name
  • Major
    The description is too short (6 words).too_short
  • 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
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_pipeline_statuses

33 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (6 words).restates_name
  • Major
    The description is too short (6 words).too_short
  • 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
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_purchase_orders

33 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (5 words).restates_name
  • Major
    The description is too short (5 words).too_short
  • 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
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_teams

33 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (7 words).restates_name
  • Major
    The description is too short (7 words).too_short
  • 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
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_vendors

33 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (5 words).restates_name
  • Major
    The description is too short (5 words).too_short
  • 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
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_custom_fields

35 / 100Rain

Purpose
13 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
0 / 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: object_type.param_no_description
  • 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
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_get_asset

36 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (7 words).restates_name
  • Major
    The description is too short (7 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: asset_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fieldpulse_get_contract

36 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (7 words).restates_name
  • Major
    The description is too short (7 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: contract_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fieldpulse_get_customer

36 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (7 words).restates_name
  • Major
    The description is too short (7 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Its description is nearly the same as fieldpulse_get_customer_contact's (similarity 0.50); only the names and schemas tell them apart. Say in this description when to use fieldpulse_get_customer_contact instead.confusable_pair
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: customer_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fieldpulse_get_estimate

36 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (7 words).restates_name
  • Major
    The description is too short (7 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: estimate_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fieldpulse_get_invoice

36 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (7 words).restates_name
  • Major
    The description is too short (7 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: invoice_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fieldpulse_get_item

36 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (8 words).restates_name
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: item_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fieldpulse_get_location

36 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (7 words).restates_name
  • Major
    The description is too short (7 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • 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

fieldpulse_get_payment

36 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (7 words).restates_name
  • Major
    The description is too short (7 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: payment_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fieldpulse_get_project

36 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (7 words).restates_name
  • Major
    The description is too short (7 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: project_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fieldpulse_get_purchase_order

36 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (8 words).restates_name
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: purchase_order_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fieldpulse_get_vendor

36 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (7 words).restates_name
  • Major
    The description is too short (7 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: vendor_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fieldpulse_list_assets

36 / 100Rain

Purpose
13 / 20
When to use
0 / 20
Arguments
16 / 25
Return value
0 / 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: status.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_payments

37 / 100Rain

Purpose
13 / 20
When to use
0 / 20
Arguments
17 / 25
Return value
0 / 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: sort_by.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_subtasks

39 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
0 / 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: status, sort_by.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_update_customer

39 / 100Rain

Purpose
20 / 20
When to use
0 / 20
Arguments
12 / 25
Return value
0 / 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: first_name, last_name, company_name, account_type, email, alt_email, secondary_email, status, notes, job_notes, has_different_billing_address, billing_address_1, billing_address_2, billing_city, billing_state, billing_zip_code, service_address_1, service_address_2, service_address_city, service_address_state, service_address_zip_code.param_no_description
  • Minor
    The meaning of the boolean argument has_different_billing_address is unclear.vague_boolean
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: customer_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fieldpulse_get_customer_contact

40 / 100Cloudy

Purpose
10 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 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
    Its description is nearly the same as fieldpulse_list_customer_contacts's (similarity 0.60); only the names and schemas tell them apart. Say in this description when to use fieldpulse_list_customer_contacts instead.confusable_pair
  • Minor
    Its description is nearly the same as fieldpulse_get_customer's (similarity 0.50); only the names and schemas tell them apart. Say in this description when to use fieldpulse_get_customer instead.confusable_pair
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: customer_id, contact_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fieldpulse_list_comments

40 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
16 / 25
Return value
0 / 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: object_type.param_no_description
  • 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
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_customer_contacts

40 / 100Cloudy

Purpose
10 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 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
    Its description is nearly the same as fieldpulse_get_customer_contact's (similarity 0.60); only the names and schemas tell them apart. Say in this description when to use fieldpulse_get_customer_contact instead.confusable_pair
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: customer_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fieldpulse_list_jobs

40 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
16 / 25
Return value
0 / 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: sort_by.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_locations

40 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
16 / 25
Return value
0 / 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: object_type.param_no_description
  • 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
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_create_customer

41 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
9 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: first_name, last_name, company_name, account_type, email, alt_email, secondary_email, status, notes, job_notes, has_different_billing_address, billing_address_1, billing_address_2, billing_city, billing_state, billing_zip_code, service_address_1, service_address_2, service_address_city, service_address_state, service_address_zip_code.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument has_different_billing_address is unclear.vague_boolean
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_company_profiles

41 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 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
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_customers

41 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
17 / 25
Return value
0 / 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: sort_by.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_job_workflow_statuses

41 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 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
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_get_job

44 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 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
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: job_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fieldpulse_list_items

44 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 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
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_users

44 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 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
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_estimates

45 / 100Cloudy

Purpose
13 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 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
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_invoices

45 / 100Cloudy

Purpose
13 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 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
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_job_status_workflows

46 / 100Cloudy

Purpose
14 / 20
When to use
5 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_list_timesheets

46 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
17 / 25
Return value
0 / 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
  • Minor
    String arguments with no constraint or example: out_time.loose_string_param
  • 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
  • Minor
    Says nothing about what it returns.no_return_info

fieldpulse_update_job

49 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
17 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Arguments without a description: customer_id, job_type, billing, subtitle, notes, field_notes, project_id, customer_contact_id.param_no_description
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: job_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fieldpulse_create_job

56 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
19 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Arguments without a description: subtitle, notes, field_notes, project_id, customer_contact_id.param_no_description
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: customer_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

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