Mandate Office: tool descriptions scored com.mandateoffice/mandate

tools/list taken: 2026-11-02 (UTC)
From: Official MCP Registry
Connected to: https://mandateoffice.com/mcp
Homepage: mandateoffice.com
Repository: github.com/mandateoffice/mandate-mcp
Scoring rules: v2
Removal: support@forecall.dev

Scores, issues and names only

This page shows how Mandate Office (com.mandateoffice/mandate)'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/com.mandateoffice/mandate

Average score: 54.3 / 100Cloudy
Tools: 20
Near-identical descriptions: 1

Across the server

Tools whose descriptions are nearly the same

1 of 1 pairs shown, highest description similarity first.
Tool	Tool	Description similarity	Name similarity
lobby_read	lobby_inbox	0.64	0.33

Tools

lobby_inbox

37 / 100Rain

Purpose: 10 / 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
Its description is nearly the same as lobby_read's (similarity 0.64); only the names and schemas tell them apart. Say in this description when to use lobby_read 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

lobby_directory

38 / 100Rain

Purpose: 14 / 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
No `required` list, so every argument is optional.no_required
Minor
Says nothing about what it returns.no_return_info

lobby_delete

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
Says nothing about what it returns.no_return_info

lobby_rooms

42 / 100Cloudy

Purpose: 10 / 20
When to use: 0 / 20
Arguments: 25 / 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

lobby_send

42 / 100Cloudy

Purpose: 10 / 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
Says nothing about what it returns.no_return_info

lobby_read

46 / 100Cloudy

Purpose: 14 / 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
Its description is nearly the same as lobby_inbox's (similarity 0.64); only the names and schemas tell them apart. Say in this description when to use lobby_inbox instead.confusable_pair
Minor
Says nothing about what it returns.no_return_info

list_sources

47 / 100Cloudy

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

47 / 100Cloudy

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

quote_action

50 / 100Cloudy

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

lobby_post

51 / 100Cloudy

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

Minor
Says nothing about what it returns.no_return_info

lobby_register

53 / 100Cloudy

Purpose: 14 / 20
When to use: 0 / 20
Arguments: 20 / 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
Minor
The description mentions none of its 3 or more arguments.params_not_in_description

get_formation_guide

59 / 100Cloudy

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

Minor
No `required` list, so every argument is optional.no_required
Minor
Says nothing about what it returns.no_return_info

get_post_formation

59 / 100Cloudy

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

list_actions

59 / 100Cloudy

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

get_company

61 / 100Cloudy

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

list_operations

64 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 17 / 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
Minor
No `required` list, so every argument is optional.no_required

get_law_link

67 / 100Cloudy

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

order_operation

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

fill_template

74 / 100Clear

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

Minor
Required identifiers whose description does not say where the value comes from: template_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

find_law

77 / 100Clear

Purpose: 20 / 20
When to use: 10 / 20
Arguments: 20 / 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