Skip to main content
Glama

Dismiss an ask

dismissAsk
DestructiveIdempotent

Drop an open ask between your company and a candidate's agent, with the reason, when the question no longer matters. The candidate's agent is told it was dropped and why. Take askId from listAsks.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "askId": "<askId>",
      "reason": "<reason>"
    },
    "name": "dismissAsk"
  }
}

Input Schema

NameRequiredDescriptionDefault
askIdYesThe askId of an open ask from listAsks.
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
reasonYesWhy the ask no longer stands, in the user's words.

Output Schema

NameRequiredDescriptionDefault
statusYes
messageYes
outcomeYesThe reason stored on the ask; a repeated dismissal keeps the first one.
closedAtYes
dismissedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so safety is largely covered. The description still adds real value beyond them: it discloses the external side effect that the candidate's agent is notified with the reason, and that inputs and results are privately recorded for usage tracking and support – context an agent could not infer from the structured fields.

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?

The core action and its trigger are front-loaded in the first sentence, with the ID sourcing and the data-recording note following. The privacy sentence is generic boilerplate, but it carries a real disclosure rather than 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?

For a destructive, idempotent mutation with an output schema present, the description covers the trigger, the required inputs' origin, the downstream notification, and data retention. It stops short of saying whether a dismissal is reversible or can be re-opened, which is the main remaining gap.

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% and the schema already says askId comes from listAsks and that reason is the user's explanation. The description restates "with the reason" and the listAsks sourcing without adding format, length, or validation guidance, so this is the baseline 3.

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?

"Drop an open ask between your company and a candidate's agent, with the reason" states a specific verb and resource, and the phrase "when the question no longer matters" bounds the operation. It does not explicitly contrast with any other closing/answering flow, but the action is unambiguous against siblings like listAsks or askCandidate.

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 conditional "when the question no longer matters" gives a clear when-to-use trigger, and "Take askId from listAsks" supplies the prerequisite source for the required identifier. No when-not-to-use case or alternative tool is named, which keeps it short of a 5.

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