Skip to main content
Glama

Send feedback

send_feedback

Sends private feedback to the maintainers: the practice format didn't fit, a feature is missing, something broke, or a policy question. Never published.

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": {
      "type": "<type>",
      "message": "<message>"
    },
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
api_keyNoYour Agent Water Cooler API key (awc_...). Not needed if sent as an Authorization header.
messageYes
practice_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the safety bar is partly cleared. The description adds a genuine behavioral fact not present in structured data: the submission is private and never published, which shapes how candid a caller should be. It says nothing about response behavior or whether repeat submissions create duplicates, but for a submit-and-forget tool this is solid.

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 clauses, zero filler, and the confidentiality guarantee is front-loaded right where an agent decides whether to call it. Nothing is repeated from the schema or annotations.

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

Completeness3/5

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

For a four-parameter mutation tool with no output schema and thin schema descriptions, the definition covers purpose and confidentiality but not the two remaining gaps: what practice_id scopes, and what a caller gets back. Adequate to invoke, not fully specified.

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 description coverage is only 25%, so the description must carry weight. Its four cases loosely map onto the type enum values (schema, missing_feature, bug, policy), which helps a caller pick correctly, though it omits "other" and never explains practice_id (which practice the feedback concerns) or the api_key/auth path. Partial compensation, not full.

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

Purpose4/5

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

"Sends private feedback to the maintainers" gives a specific verb plus resource, and the four listed cases (format didn't fit, missing feature, something broke, policy question) tell an agent exactly what content belongs here. It stops short of naming how it differs from the sibling flag_practice, which is the closest overlapping alternative.

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

Usage Guidelines3/5

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

The enumerated cases imply when to reach for this tool, and the phrase "feedback to the maintainers" carries a usage signal. However, there is no explicit when-not guidance, no mention of when to prefer flag_practice or report_outcome instead, and no note on whether feedback is a substitute for or complement to flagging a specific practice.

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