Skip to main content
Glama

searchnapply

Send feedback to searchnapply

feedback_send
Destructive

Purpose: Send the user's feedback on searchnapply to its team: a wrong answer, a fault or a suggestion, with the posting or monitor it concerns when known. When: A problem with searchnapply or its results came up and the user agreed to report it. Cost: Under 30 tokens for the reply.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "wrong-result",
      "text": "The salary filter let through a posting with no salary.",
      "about": {
        "postingId": 4711
      }
    },
    "name": "feedback_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoWhat kind of feedback it is, when the user says.
textYesThe user's feedback, 1-2000 characters, in their words.
aboutNoWhat the feedback is about, when known.

Output Schema

NameRequiredDescriptionDefault
ticketIdYesThe id the feedback was stored under.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is largely carried by structured data. The description adds that the content goes to the searchnapply team and that a reply is cheap, but it never explains why the call is flagged destructive, whether a submission can be retracted, or what confirmation comes back. The 'Cost: Under 30 tokens for the reply' line is also ambiguous about what is actually being measured.

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

Conciseness4/5

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

Three labeled lines (Purpose/When/Cost) are front-loaded and scannable, with no filler prose. The 'Cost' line is the weakest element: it is vague about what the token figure refers to and could be dropped or made concrete.

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?

With an output schema present, the description needn't explain return values, and all three parameters are covered by the schema. Purpose, trigger and consent are all stated, leaving only minor gaps around post-submission behavior and the meaning of the destructive flag.

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 100%, so kind, text and the nested about object are already fully documented with an example. The description only echoes the 'when known' qualifier for the posting/monitor reference, adding no new syntax or constraint beyond the schema. Baseline 3 is appropriate.

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?

The description names a specific verb and resource ('Send the user's feedback on searchnapply to its team') and enumerates the payload types (wrong answer, fault, suggestion) plus the optional subject (posting or monitor). No sibling tool does anything similar, so the agent can route to it unambiguously.

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

Usage Guidelines4/5

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

The 'When' line gives an explicit trigger condition plus a consent precondition ('the user agreed to report it'), which is exactly the gating an agent needs before a write. It stops short of stating when not to use it (e.g. don't send without explicit user agreement, don't use for general questions), so it is clear but not exhaustive.

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