Plumbline — a trust layer for LLM answers: tool descriptions scored com.lattice-sys.plumbline/mcp

tools/list taken: 2026-11-02 (UTC)
From: Official MCP Registry
Connected to: https://plumbline.lattice-sys.com/mcp/demo
Homepage: plumbline.lattice-sys.com
Scoring rules: v2
Removal: support@forecall.dev

Scores, issues and names only

This page shows how Plumbline — a trust layer for LLM answers (com.lattice-sys.plumbline/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/com.lattice-sys.plumbline/mcp

Average score: 69.7 / 100Cloudy
Tools: 18
Near-identical descriptions: 10

Across the server

Minor
The server has no instructions. Say there, once, what the server is for and when to use it: Claude Code and Gemini CLI read the instructions before the tool descriptions.instructions_missing

Tools whose descriptions are nearly the same

10 of 10 pairs shown, highest description similarity first.
Tool	Tool	Description similarity
compare_departments	get_manager_chain	0.73
get_manager_chain	search_employee	0.72
compare_departments	find_payroll_anomalies	0.71
find_payroll_anomalies	get_manager_chain	0.71
compare_departments	summarize_benefits	0.69
get_manager_chain	summarize_benefits	0.69
compare_departments	search_employee	0.68
find_payroll_anomalies	summarize_benefits	0.68
find_payroll_anomalies	search_employee	0.66
search_employee	summarize_benefits	0.64

Tools

ask_submit_draft

52 / 100Cloudy

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

get_ai_act_transparency

64 / 100Cloudy

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

ask_result

65 / 100Cloudy

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

No issues.

compare_departments

67 / 100Cloudy

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

Minor
Its description is nearly the same as get_manager_chain's (similarity 0.73); only the names and schemas tell them apart. Say in this description when to use get_manager_chain instead.confusable_pair
Minor
Its description is nearly the same as find_payroll_anomalies's (similarity 0.71); only the names and schemas tell them apart. Say in this description when to use find_payroll_anomalies instead.confusable_pair
Minor
Its description is nearly the same as summarize_benefits's (similarity 0.69); only the names and schemas tell them apart. Say in this description when to use summarize_benefits instead.confusable_pair
Minor
Its description is nearly the same as search_employee's (similarity 0.68); only the names and schemas tell them apart. Say in this description when to use search_employee instead.confusable_pair
Minor
String arguments with no constraint or example: a, b.loose_string_param

get_manager_chain

67 / 100Cloudy

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

Minor
Its description is nearly the same as compare_departments's (similarity 0.73); only the names and schemas tell them apart. Say in this description when to use compare_departments instead.confusable_pair
Minor
Its description is nearly the same as search_employee's (similarity 0.72); only the names and schemas tell them apart. Say in this description when to use search_employee instead.confusable_pair
Minor
Its description is nearly the same as find_payroll_anomalies's (similarity 0.71); only the names and schemas tell them apart. Say in this description when to use find_payroll_anomalies instead.confusable_pair
Minor
Its description is nearly the same as summarize_benefits's (similarity 0.69); only the names and schemas tell them apart. Say in this description when to use summarize_benefits instead.confusable_pair

search_employee

67 / 100Cloudy

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

Minor
Its description is nearly the same as get_manager_chain's (similarity 0.72); only the names and schemas tell them apart. Say in this description when to use get_manager_chain instead.confusable_pair
Minor
Its description is nearly the same as compare_departments's (similarity 0.68); only the names and schemas tell them apart. Say in this description when to use compare_departments instead.confusable_pair
Minor
Its description is nearly the same as find_payroll_anomalies's (similarity 0.66); only the names and schemas tell them apart. Say in this description when to use find_payroll_anomalies instead.confusable_pair
Minor
Its description is nearly the same as summarize_benefits's (similarity 0.64); only the names and schemas tell them apart. Say in this description when to use summarize_benefits instead.confusable_pair

trust_finalize

67 / 100Cloudy

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

run_sql

68 / 100Cloudy

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

cross_check

69 / 100Cloudy

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

find_payroll_anomalies

69 / 100Cloudy

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

Minor
Its description is nearly the same as compare_departments's (similarity 0.71); only the names and schemas tell them apart. Say in this description when to use compare_departments instead.confusable_pair
Minor
Its description is nearly the same as get_manager_chain's (similarity 0.71); only the names and schemas tell them apart. Say in this description when to use get_manager_chain instead.confusable_pair
Minor
Its description is nearly the same as summarize_benefits's (similarity 0.68); only the names and schemas tell them apart. Say in this description when to use summarize_benefits instead.confusable_pair
Minor
Its description is nearly the same as search_employee's (similarity 0.66); only the names and schemas tell them apart. Say in this description when to use search_employee instead.confusable_pair

get_answer_queries

70 / 100Clear

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

No issues.

query_fact

70 / 100Clear

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

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

run_code

70 / 100Clear

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

search_docs

72 / 100Clear

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

No issues.

summarize_benefits

74 / 100Clear

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

Minor
Its description is nearly the same as compare_departments's (similarity 0.69); only the names and schemas tell them apart. Say in this description when to use compare_departments instead.confusable_pair
Minor
Its description is nearly the same as get_manager_chain's (similarity 0.69); only the names and schemas tell them apart. Say in this description when to use get_manager_chain instead.confusable_pair
Minor
Its description is nearly the same as find_payroll_anomalies's (similarity 0.68); only the names and schemas tell them apart. Say in this description when to use find_payroll_anomalies instead.confusable_pair
Minor
Its description is nearly the same as search_employee's (similarity 0.64); only the names and schemas tell them apart. Say in this description when to use search_employee instead.confusable_pair
Minor
No `required` list, so every argument is optional.no_required

get_evidence_document

75 / 100Clear

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

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

describe_fact_capabilities

82 / 100Clear

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

No issues.

ask_prepare

87 / 100Clear

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