Forecall
Failure recordsDocs
All scored servers

SteadyFetch: tool descriptions scored

tools/list taken
(UTC)
From
smithery.ai/servers/intake-triage/steadyfetch
Scoring rules
v2

Scores, issues and names only

This page shows how SteadyFetch'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/intake-triage-steadyfetch
Average score
49.0 / 100Cloudy
Tools
5
Near-identical descriptions
0

Across the server

No server-wide issues.

Tools

fetch_markdown

40 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
0 / 25
Return value
15 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Major
    Arguments without a description: url, wait_for, use_cache.param_no_description
  • Minor
    String arguments with no constraint or example: url.loose_string_param
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument use_cache is unclear.vague_boolean
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

fetch_url

40 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
0 / 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
  • Major
    Arguments without a description: url, wait_for, js_render, use_cache.param_no_description
  • Minor
    String arguments with no constraint or example: url.loose_string_param
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument js_render is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument use_cache is unclear.vague_boolean
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

check_domain

45 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
0 / 25
Return value
15 / 15
Constraints and side effects
0 / 10
Examples
5 / 10
  • Major
    Arguments without a description: domain.param_no_description
  • Minor
    String arguments with no constraint or example: domain.loose_string_param
  • 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

cache_stats

55 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
0 / 10
Examples
0 / 10
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

clear_cache

65 / 100Cloudy

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