Surfing Dog: tool descriptions scored ai.surfingdog/search

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

Scores, issues and names only

This page shows how Surfing Dog (ai.surfingdog/search)'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/ai.surfingdog/search

Average score: 65.8 / 100Cloudy
Tools: 22
Near-identical descriptions: 1

Across the server

Minor
The server's instructions are 2430 characters. Claude Code reads only the first 2,048 by default (Codex 0.154.0 reads them whole). Put what the server is for first.instructions_long

Tools whose descriptions are nearly the same

1 of 1 pairs shown, highest description similarity first.
Tool	Tool	Description similarity	Name similarity
ask_business	request_quote	0.61	0.00

Tools

room_invite

47 / 100Cloudy

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

Major
Arguments without a description: seat.param_no_description
Minor
Says nothing about what it returns.no_return_info

room_leave

52 / 100Cloudy

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

Major
Arguments without a description: seat, close, summary, report, report.reason, report.details.param_no_description
Minor
The meaning of the boolean argument close is unclear.vague_boolean
Minor
Says nothing about what it returns.no_return_info

list_categories

54 / 100Cloudy

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

room_send

55 / 100Cloudy

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

Major
Arguments without a description: seat, text, done.param_no_description
Minor
The meaning of the boolean argument done is unclear.vague_boolean
Minor
Says nothing about what it returns.no_return_info

update_business

55 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 18 / 25
Return value: 8 / 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
Arguments without a description: domain, doors, doors.add, doors.add[].terms_url, opt_out.scopes, proof, proof.challenge_id, proof.method.param_no_description

list_attributes

57 / 100Cloudy

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

58 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 21 / 25
Return value: 8 / 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
Arguments without a description: near.lat, near.lng.param_no_description

get_census

60 / 100Cloudy

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

start_inbox

60 / 100Cloudy

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

register_business

63 / 100Cloudy

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

Minor
Arguments without a description: category.alternates, doors, doors[].terms_url, hours.closures, hours.closures[].from, hours.closures[].to, hours.timezone, hours.weekly, proof, proof.challenge_id, proof.method, want_inbox, where.address, where.address.country, where.address.locality, where.address.postal_code, where.address.region, where.address.street, where.geo, where.geo.lat, where.geo.lng, where.kind, where.service_area, where.ships_to.param_no_description
Minor
The meaning of the boolean argument want_inbox is unclear.vague_boolean

report_door

63 / 100Cloudy

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

Minor
Arguments without a description: reports, reports[].door, reports[].result, v.param_no_description
Minor
The description mentions none of its 3 or more arguments.params_not_in_description

check_dns

65 / 100Cloudy

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

get_business

65 / 100Cloudy

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

room_wait

72 / 100Clear

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

Minor
Arguments without a description: seat, wait_seconds.param_no_description

request_quote

73 / 100Clear

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

Minor
Its description is nearly the same as ask_business's (similarity 0.61); only the names and schemas tell them apart. Say in this description when to use ask_business instead.confusable_pair

search_products

74 / 100Clear

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

Minor
Arguments without a description: near.lat, near.lng.param_no_description
Minor
No `required` list, so every argument is optional.no_required

search_businesses

75 / 100Clear

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

Minor
No `required` list, so every argument is optional.no_required

room_join

77 / 100Clear

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

Minor
Arguments without a description: code_or_link.param_no_description

check_business

78 / 100Clear

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

No issues.

request_booking

80 / 100Clear

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

No issues.

room_open

81 / 100Clear

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

Minor
No `required` list, so every argument is optional.no_required

ask_business

83 / 100Clear

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

Minor
Its description is nearly the same as request_quote's (similarity 0.61); only the names and schemas tell them apart. Say in this description when to use request_quote instead.confusable_pair

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