All scored servers

Bounty Engineer Agent Commerce: tool descriptions scored io.github.gatoprd/bounty-engineer

tools/list taken
(UTC)
Connected to
https://bounty-engineer-x402-prod.onrender.com/mcp
Scoring rules
v2
Score this URL as it is today

Scores, issues and names only

This page shows how Bounty Engineer Agent Commerce (io.github.gatoprd/bounty-engineer)'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.gatoprd/bounty-engineer
Average score
64.5 / 100Cloudy
Tools
22
Near-identical descriptions
0

Across the server

No server-wide issues.

Tools

get_product_proof

46 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
10 / 25
Return value
7 / 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: product_id.param_no_description
  • Minor
    Required identifiers whose description does not say where the value comes from: product_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

paid_agent_purchase_firewall

46 / 100Cloudy

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

paid_x402_payment_preflight

49 / 100Cloudy

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

list_products

55 / 100Cloudy

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

get_commerce_radar_offer

56 / 100Cloudy

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

paid_funding_loop

56 / 100Cloudy

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

paid_mcp_manifest_security

57 / 100Cloudy

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

paid_funding_rates

59 / 100Cloudy

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

paid_web_extract

59 / 100Cloudy

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

paid_merchant_feed_audit

62 / 100Cloudy

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

get_purchase_instructions

66 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
25 / 25
Return value
7 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Required identifiers whose description does not say where the value comes from: product_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

paid_json_contract_check

66 / 100Cloudy

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

quote_premium_delivery

67 / 100Cloudy

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

No issues.

quote_premium_workload

70 / 100Clear

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

quote_autonomous_purchase

71 / 100Clear

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

No issues.

get_workflow_recipe

72 / 100Clear

Purpose
20 / 20
When to use
0 / 20
Arguments
25 / 25
Return value
7 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

list_premium_agent_packs

72 / 100Clear

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

quote_instant_work

74 / 100Clear

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

No issues.

qualify_premium_buyer

75 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
25 / 25
Return value
0 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Minor
    Says nothing about what it returns.no_return_info

quote_batch_web_intelligence

77 / 100Clear

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

No issues.

recommend_paid_tool

77 / 100Clear

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

No issues.

execute_paid_product

87 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
25 / 25
Return value
7 / 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