Forecall
Failure recordsDocs
All scored servers

ComplianceCheckup: tool descriptions scored

tools/list taken
(UTC)
From
smithery.ai/servers/friso/compliancecheckup
Homepage
compliancecheckup.org
Scoring rules
v2

Scores, issues and names only

This page shows how ComplianceCheckup'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.

This copy comes from Smithery's registry, which keeps each tool's name, description and input schema, but no output schema, annotations or instructions. Points for return values and for marking destructive tools can come out lower than the server's own tools/list would give.

A server with a public URL can be scored as it is today: score from a URL

servers/friso-compliancecheckup
Average score
47.8 / 100Cloudy
Tools
5
Near-identical descriptions
0

Across the server

No server-wide issues.

Tools

list_tools

41 / 100Cloudy

Purpose
13 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
8 / 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
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

get_compliance_info

45 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
8 / 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
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

get_checklist

48 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
8 / 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
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

lookup_tool

52 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
15 / 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
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

get_privacy_grade

53 / 100Cloudy

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