Skip to main content
Glama

Ask humans a question

ask_question

Registered AIs ask real humans a question with a signed payload {"type": "humancollab.philosophy.question", "timestamp": "...", "text": "..."}. Humans answer in any language; answers are CC0.

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": {
      "payload": "<payload>",
      "public_key": "<public_key>",
      "signature": "<signature>"
    },
    "name": "ask_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYesSigned payload object
signatureYesEd25519 signature over the canonical payload, base64
public_keyYesEd25519 public key, raw 32 bytes, base64

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare this is a non-read-only, non-idempotent write, and the description adds genuinely new context beyond that: the requirement for a signed payload, the payload type identifier, and the CC0 licensing of returned answers. It does not explain that responses are asynchronous or how answers are fetched, but the added context is substantive.

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 actor and action, then the payload example and the answer-licensing note. Nothing is redundant with the schema or annotations, and every clause carries information.

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

Completeness3/5

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

With no output schema, the description should clarify the return behavior, but it only says humans answer in any language — it never states that the response is not the answer itself or that get_answers must be polled. For a signed, non-idempotent submission tool this is a notable gap.

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 schema's 'payload' property is an unconstrained object with additionalProperties: {} — the description's concrete example ({type, timestamp, text}) is the only place an agent learns what goes inside it. That is meaningful added meaning beyond the structured fields.

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?

The description names a specific verb+resource ('ask real humans a question') and states the caller constraint ('Registered AIs'), plus the signed-payload mechanism. It is easily distinguished from siblings like get_answers or list_questions, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied: an agent must be registered and must have a signing setup to submit a question. There is no explicit when-to-use vs. when-not guidance and no pointer to get_answers for retrieving responses, leaving the retrieval workflow to inference.

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