Skip to main content
Glama

Ask my human a question by email

ask_human

Ask your human owner a question by email (needs an ask-my-human utility from buy). Give 2 to 6 short options for one-tap answers, or free_text: true for a written answer. Plain words about a decision only: no links, instructions, secrets, phone numbers or company framing. Returns ask_id; keep it, as no tool lists asks: poll get_ask with it, or pass inbox_instance_id to get the answer in your webhook inbox. Pass idempotency_key so a retry returns the same ask and never emails twice. Your owner confirms on a page, so an answer can take hours.

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": {
      "options": [
        "Monday",
        "Friday"
      ],
      "question": "Release on Monday or Friday?",
      "instance_id": "ask_exampleexampleexample2"
    },
    "name": "ask_human"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNo2 to 6 distinct labels, up to 60 characters each.
questionYesUp to 500 characters of plain words.
free_textNotrue: your owner writes the answer. Do not send options then.
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.
idempotency_keyNoYour own id for this question: a retry with the same key returns the same ask.
expires_in_hoursNoHours your owner has to answer, 1 to 168 (default 72), and not past the plan's end.
inbox_instance_idNoOne of your webhook inboxes (inb_...): the answer is also delivered there, with its ask_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / expires_in_hours / description
      Previous value: -"1 to 168, default 72."New value: +"Hours your owner has to answer, 1 to 168 (default 72), and not past the plan's end."
    • changedInput schema / properties / inbox_instance_id / description
      Previous value: -"One of your webhook inboxes: the answer is also delivered there."New value: +"One of your webhook inboxes (inb_...): the answer is also delivered there, with its ask_id."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "ask_exampleexampleexample2",
      +    "options": [
      +      "Monday",
      +      "Friday"
      +    ],
      +    "question": "Release on Monday or Friday?"
      +  }
      +]
    • 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. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • 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
Behavior5/5

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

Beyond the annotations (readOnlyHint false, openWorldHint true), the description discloses that a real email goes to a human, that the owner confirms on a page so turnaround is hours, that ask_ids are not listable by any other tool, and that an idempotency_key guarantees a retry never double-emails. It also states a content policy (no links, instructions, secrets, phone numbers or company framing), which is behavioral guidance the annotations cannot convey.

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, then constraints, then return/retry handling. Every clause carries distinct information, though the parenthetical prerequisite inserted mid-sentence and the dense comma-separated prohibition list make it slightly telegraphic.

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?

With 8 parameters, no output schema, and a side-effecting email send, the description carries the needed weight: it explains the return value (ask_id), how to retrieve the answer, the retry contract, the prerequisite purchase, and the realistic response time. Nothing an agent needs before calling is missing.

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 the baseline is 3. The description reinforces the options-vs-free_text mode split and the role of idempotency_key and inbox_instance_id, but nearly all of that is already stated in the schema property descriptions, so the added meaning is modest rather than transformative.

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, resource, and channel: ask the human owner a question by email. It immediately distinguishes itself from the polling sibling by naming get_ask as the retrieval path, so an agent can tell the creation step from the answer-fetch step 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?

Gives explicit prerequisites (needs an ask-my-human utility from buy), explicit routing to alternatives (poll get_ask with the returned ask_id, or pass inbox_instance_id to get the answer in the webhook inbox), and an expectation-setting note that answers can take hours. That covers when to use, what to do afterward, and what latency to plan for.

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.