Skip to main content
Glama

reject

Report that a user rejected the answer to a query, demoting the recalled retrieval path and ensuring the question gets a fresh search next time.

Instructions

Report that the user rejected the answer to query. Pass the same question that was given to recall: the path recalled for it is demoted and the question gets a fresh search next time.

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": {
      "query": "<query>"
    },
    "name": "reject"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is not read-only and not destructive; the description goes beyond them by disclosing the actual side effect — the previously recalled path is demoted and the question will be re-searched later. That is exactly the behavioral context an agent needs before mutating state. It does not address what happens on repeat calls, despite idempotentHint=false implying compounding demotion.

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 sentences, front-loaded with the action, followed by the input constraint and the consequence. No filler, no restatement of the tool name, and the operational detail an agent needs appears before the explanatory clause.

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?

For a one-parameter feedback tool with no output schema, this covers purpose, required input semantics, and result. The remaining gaps are edge behavior (no matching recall, repeated rejections) rather than anything that would prevent a correct invocation.

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

Parameters4/5

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

With 0% schema description coverage, the schema offers only a bare string 'Query'. The description compensates by requiring 'the same question that was given to `recall`', which communicates that this is an exact-match reference to a prior call rather than an arbitrary search string. It stops short of saying what happens when no matching recall exists.

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 ('Report that the user rejected') tied to a specific resource ('the answer to `query`'), and then names the effect on the knowledge store: the recalled path is demoted and a fresh search happens next time. It also anchors itself to the sibling `recall`, so an agent can tell this apart from `record` without opening either schema.

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 description makes the trigger context clear: this is called after `recall` has produced an answer the user rejected, and the same question must be supplied. It does not state explicit exclusions or what to do for related-but-different feedback (e.g. correcting rather than rejecting), so it falls short of a full when/when-not pairing.

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

Deploy Server

Other Tools