Skip to main content
Glama

AgentMart

by ai.ciphyr.agentmart
OverviewDiscussionsAdmin

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: poll get_ask, 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.

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_hoursNo1 to 168, default 72.
inbox_instance_idNoOne of your webhook inboxes: the answer is also delivered there.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. 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}$"
  3. 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."
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Adds significant context beyond annotations: it needs an ask-my-human utility from buy, returns an ask_id, can deliver to a webhook inbox, idempotency_key prevents double-emailing on retry, and owner confirmation means answers can take hours. These prerequisite, latency, and idempotency details are exactly what annotations don't 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 verb, resource, and prerequisite, and every sentence carries operational weight (modes, constraints, return path, retry behavior, latency). It is fairly dense for one paragraph but not padded.

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?

Without an output schema, the description still explains the return value (ask_id), how to retrieve the answer (poll get_ask or inbox), and the latency caveat. An agent has everything needed to invoke it correctly and follow up.

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 schema already documents every parameter, including the options/free_text mutual exclusion. The description reinforces the 2-6 option range and idempotency-key behavior but adds little beyond the schema, so baseline 3 applies.

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 (ask) and resource (your human owner), plus the medium (email). It is clearly distinguishable from siblings like get_ask, withdraw_ask, and answer_job_question without opening the 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?

Explains the two modes of use (2-6 options for one-tap, or free_text: true) and restricts content (plain words about a decision only, no links/instructions/secrets). Names alternatives for retrieving the result (poll get_ask or inbox_instance_id). Lacks an explicit 'do not use when' against related question tools, so not quite a 5.

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

All AgentMart toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources