Ask a human expert

submit_request

Send a problem to Cristian Desivo, a human expert, for his most creative solution idea. Payment first: unless get_status shows free_trial, pay 20 USD by PayPal, either at https://paypal.me/CristianDesivo/20USD or by sending it to cdesivo92@gmail.com (an agent with PayPal API access, for example the Payouts API, can do this on its own), then pass the PayPal transaction ID; this tool takes no payments. The summary is all I read for the first reply (300 words at most). I write the reply myself and it arrives by email at reply_email, not through this server: within 15 minutes while I'm online, otherwise by 09:30 UTC. A confirmation email goes to reply_email right away. At most 5 requests per hour from one address.

Input Schema

Name	Required	Description
`name`	No	Optional: your or your user's name
`summary`	Yes	The problem in 300 words or fewer: what it is, what has been tried, the key constraints, and the deadline
`payer_email`	No	Optional: the email of the PayPal account that paid, in case PayPal shows different transaction IDs
`paypal_name`	No	Optional: the name on the PayPal account that paid, for the same reason
`reply_email`	Yes	Where the confirmation and my reply go
`transaction_id`	No	The PayPal transaction ID (17 letters and digits) of the payment made at pay_url or sent by PayPal to paypal_email. Required unless get_status shows free_trial

Output Schema

Name	Required	Description
`errors`	No	When not sent: the problem with each field (or 'form')
`received`	Yes	True if the request was sent
`reply_to`	No
`first_reply`	No
`confirmation`	No
`transaction_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 25, 2026

addedInput schema / properties / payer_email

Added value: +{
+  "description": "Optional: the email of the PayPal account that paid, in case PayPal shows different transaction IDs",
+  "type": "string"
+}

changedInput schema / properties / paypal_name / description

Previous value: -"Optional: the name on the PayPal account that paid, in case PayPal shows different transaction IDs"New value: +"Optional: the name on the PayPal account that paid, for the same reason"

changedInput schema / properties / transaction_id / description

Previous value: -"The PayPal transaction ID (17 letters and digits) of the payment a human made at pay_url. Required unless get_status shows free_trial"New value: +"The PayPal transaction ID (17 letters and digits) of the payment made at pay_url or sent by PayPal to paypal_email. Required unless get_status shows free_trial"

First observedOct 25, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say this is non-read-only, non-destructive and open-world; the description goes far beyond that by disclosing the 20 USD payment requirement, that the tool itself takes no payments, that the reply arrives by email outside this server, expected latency (15 minutes when online, otherwise 09:30 UTC), an immediate confirmation email, and a 5-requests-per-hour rate limit. That is unusually rich disclosure of side effects and external dependencies.

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?

Purpose is front-loaded and nearly every sentence carries operational weight — payment, word limit, delivery channel, timing, rate limit. The prose is a dense wall of clauses with the payment mechanics spliced mid-paragraph, which hurts scanability, but little is genuinely expendable.

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 an open-world, non-idempotent tool with an output schema, the description covers everything an agent needs before calling: cost, payment mechanics, required transaction ID, content limits, delivery channel, turnaround time, and throttling. Return values are handled by the output schema, so no gap remains.

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 already 100%, so the baseline is 3; the description adds meaning on top by explaining the transaction_id payment precondition tied to get_status, the 300-word cap on summary ('all I read for the first reply'), and that reply_email receives both the confirmation and the human reply. Slight redundancy with the schema descriptions keeps it from a 5.

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?

Opens with a specific verb and resource — send a problem to a named human expert for a creative solution idea — which is unmistakably distinct from the sibling tools get_status (payment/trial state) and get_terms. An agent knows exactly what this tool accomplishes 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 Guidelines5/5

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

Gives explicit preconditions and the alternative path: 'unless get_status shows free_trial, pay 20 USD by PayPal... then pass the PayPal transaction ID'. It names the sibling tool to consult and the exact condition under which payment can be skipped, leaving nothing to inference.

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

All Ask a human expert tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?