All scored servers

gl.parse/mcp: tool descriptions scored

tools/list taken
(UTC)
Connected to
https://mcp.parse.gl/mcp
Scoring rules
v2
Score this URL as it is today

Scores, issues and names only

This page shows how gl.parse/mcp'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/gl.parse/mcp
Average score
74.2 / 100Clear
Tools
35
Near-identical descriptions
1

Across the server

  • Minor
    35 tools. Above 25, models start to tell tools apart less well.many_tools

Tools whose descriptions are nearly the same

1 of 1 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
parse_dismiss_taskparse_restore_task0.610.50

Tools

fetch

29 / 100Rain

Purpose
14 / 20
When to use
0 / 20
Arguments
3 / 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
  • Major
    Arguments without a description: id.param_no_description
  • Minor
    String arguments with no constraint or example: id.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

parse_dashboard_members

35 / 100Rain

Purpose
13 / 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: page.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

search

37 / 100Rain

Purpose
14 / 20
When to use
5 / 20
Arguments
11 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Arguments without a description: limit.param_no_description
  • Minor
    Says nothing about what it returns.no_return_info

parse_search

44 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
13 / 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
  • Minor
    Arguments without a description: limit.param_no_description

parse_dashboard_answer

50 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
10 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: brandSlug, marketId, id, executedAt.param_no_description
  • Minor
    Required identifiers whose description does not say where the value comes from: marketId, id. Name the tool or the place that returns it, or models look it up first.id_source_missing

parse_dashboard_workspace

57 / 100Cloudy

Purpose
20 / 20
When to use
10 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Arguments without a description: offset, includePlan, includeConnections.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
    The meaning of the boolean argument includePlan is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument includeConnections is unclear.vague_boolean

parse_dashboard_answers

62 / 100Cloudy

Purpose
20 / 20
When to use
10 / 20
Arguments
10 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: brandSlug, query, query.v, query.market, query.window, query.brand, query.brand.id, query.brand.rule, query.insteadOf, query.tone, query.reason, query.theme, query.need, query.needs, query.engine, query.site, query.page, query.search, query.question, query.signal, query.groupSort, query.groupSort.column, query.groupSort.direction, group, page, includeFilters, continuation, continuation.pin, continuation.table, continuation.offset.param_no_description
  • Minor
    String arguments with no constraint or example: query.site.loose_string_param
  • Minor
    The meaning of the boolean argument includeFilters is unclear.vague_boolean

parse_get_question

62 / 100Cloudy

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

No issues.

parse_why

69 / 100Cloudy

Purpose
20 / 20
When to use
10 / 20
Arguments
12 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Arguments without a description: offset, weeks.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

parse_get_brand

72 / 100Clear

Purpose
20 / 20
When to use
5 / 20
Arguments
15 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Minor
    Arguments without a description: section.param_no_description

parse_get_topic

72 / 100Clear

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

No issues.

parse_what_changed

73 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
11 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Arguments without a description: offset, marketId, sections.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

parse_check_brand

75 / 100Clear

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

No issues.

parse_evidence

76 / 100Clear

Purpose
20 / 20
When to use
10 / 20
Arguments
14 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Major
    Arguments without a description: reference, offset, includeHistory.param_no_description
  • Minor
    The meaning of the boolean argument includeHistory is unclear.vague_boolean

parse_pitch_check

78 / 100Clear

Purpose
20 / 20
When to use
10 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

parse_add_topic

80 / 100Clear

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

No issues.

parse_correct_rival

80 / 100Clear

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

parse_dismiss_task

80 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Its description is nearly the same as parse_restore_task's (similarity 0.61); only the names and schemas tell them apart. Say in this description when to use parse_restore_task instead.confusable_pair
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

parse_next_tasks

80 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
13 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Major
    Arguments without a description: marketId, mine, status, offset.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
    The meaning of the boolean argument mine is unclear.vague_boolean

parse_remove_topic

80 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Required identifiers whose description does not say where the value comes from: topicId. Name the tool or the place that returns it, or models look it up first.id_source_missing

parse_restore_task

80 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Its description is nearly the same as parse_dismiss_task's (similarity 0.61); only the names and schemas tell them apart. Say in this description when to use parse_dismiss_task instead.confusable_pair
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

parse_set_notification

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
  • Minor
    Arguments without a description: enabled.param_no_description
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument enabled is unclear.vague_boolean

parse_undo_sent

80 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

parse_record_reply

84 / 100Clear

Purpose
20 / 20
When to use
20 / 20
Arguments
24 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Arguments without a description: from.name.param_no_description
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

parse_answer_question

85 / 100Clear

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

parse_correct_mention

85 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

parse_save_message

85 / 100Clear

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

parse_set_sender_name

85 / 100Clear

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

No issues.

parse_questions

87 / 100Clear

Purpose
20 / 20
When to use
10 / 20
Arguments
22 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
  • Minor
    No `required` list, so every argument is optional.no_required

parse_tracking

87 / 100Clear

Purpose
20 / 20
When to use
10 / 20
Arguments
22 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
  • Minor
    No `required` list, so every argument is optional.no_required

parse_mark_sent

91 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
24 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Minor
    Arguments without a description: to.name.param_no_description

parse_app_link

92 / 100Clear

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

No issues.

parse_audit

92 / 100Clear

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

parse_task

95 / 100Clear

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

parse_track_brand

97 / 100Clear

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