Skip to main content
Glama

Supersurf

Send feedback

send_feedback

Use this when the person asks to tell Supersurf something: a wrong forecast, a missing spot, an idea. Only their words, never include the conversation. Not for questions about the surf: answer from the other tools.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>",
      "text": "<text>"
    },
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesproblem, idea or question
textYes
toolNo

Output Schema

NameRequiredDescriptionDefault
sentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations cover safety (non-read-only, non-destructive, closed-world), and the description adds a genuinely useful behavioral rule: relay only the person's own words, never the conversation context. It stops short of describing what happens after submission or what the response contains, so it is strong but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences plus a negative clause, with the usage trigger front-loaded and the exclusion last. Every clause carries information; nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the trigger plus privacy constraint cover the main behavioral risks of a submit tool. The notable remaining gap is the undocumented 'tool' parameter, which an agent must guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%: 'kind' is documented inline, but 'text' and 'tool' are not. The line 'Only their words' partly clarifies that 'text' should be verbatim user wording, which is real added meaning, but the 'tool' parameter is left entirely unexplained in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('tell Supersurf something') and grounds it with concrete examples: a wrong forecast, a missing spot, an idea. It also distinguishes the tool from the surf-information siblings by ruling those out at the end.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both when-to-use ('when the person asks to tell Supersurf something') and when-not ('Not for questions about the surf: answer from the other tools'), and names where to go instead. No inference required to route correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources