Forecall
Failure recordsDocs
All scored servers

tw.tobid/tenders: tool descriptions scored

tools/list taken
(UTC)
From
Official MCP Registry
Connected to
https://api.tobid.tw/mcp
Homepage
tobid.tw/guide/mcp
Scoring rules
v2
Removal
support@forecall.dev
Score this URL as it is today

Scores, issues and names only

This page shows how tw.tobid/tenders'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/tw.tobid/tenders
Average score
15.7 / 100Rain
Tools
22
Near-identical descriptions
1

Across the server

Tools whose descriptions are nearly the same

1 of 1 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
vendor_compliancevendor_committee1.000.33

Tools

unit_committee

9 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
3 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    The description only restates the name (2 words).restates_name
  • Major
    The description is too short (2 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: unit.param_no_description
  • Minor
    String arguments with no constraint or example: unit.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

unit_report

9 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
3 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    The description only restates the name (4 words).restates_name
  • Major
    The description is too short (4 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: unit.param_no_description
  • Minor
    String arguments with no constraint or example: unit.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

bid_strategy

13 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
3 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    The description is too short (4 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: unit_id, job_number.param_no_description
  • Minor
    String arguments with no constraint or example: unit_id, job_number.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints
  • Minor
    Required identifiers whose description does not say where the value comes from: unit_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

committee_member

13 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
3 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    The description is too short (1 word).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: 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
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

compare_vendors

13 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
3 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    The description is too short (3 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: vendor_a, vendor_b.param_no_description
  • Minor
    String arguments with no constraint or example: vendor_a, vendor_b.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

evaluation_committee

13 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
3 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: unit_id, job_number.param_no_description
  • Minor
    String arguments with no constraint or example: unit_id, job_number.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints
  • Minor
    Required identifiers whose description does not say where the value comes from: unit_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

find_entity

13 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
3 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    The description is too short (3 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: q.param_no_description
  • Minor
    String arguments with no constraint or example: q.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

get_tender

13 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
3 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • 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
  • Major
    Arguments without a description: unit_id, job_number.param_no_description
  • Minor
    String arguments with no constraint or example: unit_id, job_number.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints
  • Minor
    Required identifiers whose description does not say where the value comes from: unit_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

likely_bidders

13 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
3 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: unit_id, job_number.param_no_description
  • Minor
    String arguments with no constraint or example: unit_id, job_number.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints
  • Minor
    Required identifiers whose description does not say where the value comes from: unit_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

price_analysis

13 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
3 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    The description is too short (1 word).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: unit_id, job_number.param_no_description
  • Minor
    String arguments with no constraint or example: unit_id, job_number.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints
  • Minor
    Required identifiers whose description does not say where the value comes from: unit_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

search_committee_members

13 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
3 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: q.param_no_description
  • Minor
    String arguments with no constraint or example: q.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

vendor_committee

13 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
3 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    The description is too short (1 word).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: name.param_no_description
  • Minor
    Its description is nearly the same as vendor_compliance's (similarity 1.00); only the names and schemas tell them apart. Say in this description when to use vendor_compliance instead.confusable_pair
  • Minor
    String arguments with no constraint or example: name.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

vendor_compliance

13 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
3 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    The description is too short (1 word).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: name.param_no_description
  • Minor
    Its description is nearly the same as vendor_committee's (similarity 1.00); only the names and schemas tell them apart. Say in this description when to use vendor_committee instead.confusable_pair
  • Minor
    String arguments with no constraint or example: name.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

vendor_report

13 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
3 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    The description is too short (2 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: 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
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

procurement_forecast

15 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
5 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • 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
  • Major
    Arguments without a description: q, unit, limit, include_past.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument include_past is unclear.vague_boolean
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

public_reading

15 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
5 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • 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
  • Major
    Arguments without a description: q, unit, limit, include_closed.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument include_closed is unclear.vague_boolean
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

vendor_awards

18 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
5 / 25
Return value
0 / 15
Constraints and side effects
3 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: name, year, unit_id, page, limit.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

asset_sales

19 / 100Rain

Purpose
14 / 20
When to use
0 / 20
Arguments
5 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: q, kind, open_only, limit.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument open_only is unclear.vague_boolean
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

search_tenders

19 / 100Rain

Purpose
14 / 20
When to use
0 / 20
Arguments
5 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: q, kind, region, year, unit_id, unit_name, vendor, budget_min, budget_max, page.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

subcontract_opportunities

24 / 100Rain

Purpose
14 / 20
When to use
0 / 20
Arguments
5 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: q, mode, region, category, vendor, days, sort, limit, page.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

framework_contracts

27 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
5 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: q, vendor, unit_id, year, limit, page, mode.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

hot_opportunities

35 / 100Rain

Purpose
10 / 20
When to use
0 / 20
Arguments
25 / 25
Return value
0 / 15
Constraints and side effects
0 / 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
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

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