Skip to main content
Glama

Delete a question to my human

delete_ask
DestructiveIdempotent

Delete an answered or expired question to your owner, with its answer, for good (no undo). With older_too: true, also every older answered or expired ask of the plan, keeping those not done (kept_pending, kept_withdrawn). Alone, a question still waiting answers 409 ask_pending (withdraw_ask stops it), and a withdrawn one can go only after its expires_at. Works after the plan ended too.

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": {
      "ask_id": "qst_exampleexampleexample2",
      "instance_id": "ask_exampleexampleexample2"
    },
    "name": "delete_ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
ask_idYesask_id (qst_...) from ask_human.
older_tooNotrue: also delete every older answered or expired ask.
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ask_id / description
      Previous value: -"ask_id from ask_human."New value: +"ask_id (qst_...) from ask_human."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "ask_id": "qst_exampleexampleexample2",
      +    "instance_id": "ask_exampleexampleexample2"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  3. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  4. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / ask_id / description
      Added value: +"ask_id from ask_human."
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
  5. First observed

TDQS

A4.6/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 readOnlyHint=false, so the safety profile is known; the description adds the stronger claim of no undo, the exact cascade scope of older_too (only answered/expired asks, keeping kept_pending and kept_withdrawn), the 409 error surfaced on pending asks, and the post-plan availability. That is real added behavior beyond the annotations, though it does not describe the success response or whether the answer payload is echoed back.

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?

Front-loaded with the core action and the no-undo warning, and nearly every clause carries information (older_too scope, 409, withdraw_ask route, expires_at, post-plan). The phrasing is telegraphic in places ("With older_too: true, also every older answered or expired ask of the plan"), requiring a second read, which keeps it from a 5.

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

Completeness5/5

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

For a four-parameter destructive tool with no output schema, the description covers destruction scope, cascade behavior, failure mode with the correct fallback, timing precondition, and lifecycle edge case. Nothing an agent needs in order to call this correctly, or to know when to avoid it, is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further on older_too by stating what the cascade preserves (kept_pending, kept_withdrawn) and by tying ask_id to the pending/withdrawn timing rules. It adds semantics the schema's one-line param note does not carry.

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 ("Delete an answered or expired question... with its answer") and immediately scopes it ("for good (no undo)"). It also distinguishes itself from the nearest sibling by naming withdraw_ask for the pending case, so an agent can separate the two 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 Guidelines5/5

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

Explicit when-not guidance is given: a still-pending question returns 409 ask_pending and the agent should use withdraw_ask, and a withdrawn ask can only be removed after expires_at. It also spells out the conditional path (older_too: true) and the edge case that it works after the plan ended, covering use, exclusion, and alternative in one paragraph.

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.