Ask a human expert

Offer terms

get_terms

Read-only

The offer's full terms, in English: who answers, what you get, the price, hours, when first replies come, the PayPal pay_url, and how to submit a request.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`hours`	Yes
`price`	Yes
`submit`	No	The same request as a plain HTTP form/JSON POST
`pay_url`	Yes	Where a human pays before submit_request
`good_fit`	No
`hours_et`	No
`hours_utc`	No
`not_a_fit`	No
`background`	No
`pay_by_api`	No
`larger_work`	No
`open_to_any`	No
`who_answers`	No
`paypal_email`	No	The PayPal account to send the payment to, e.g. with the Payouts API
`summary_rule`	No
`what_you_get`	Yes
`request_email`	No
`request_steps`	Yes
`note_for_agents`	No
`first_reply_online`	No
`summary_word_limit`	Yes
`first_reply_offline`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

addedOutput schema / properties / pay_by_api
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / paypal_email

Added value: +{
+  "description": "The PayPal account to send the payment to, e.g. with the Payouts API",
+  "type": "string"
+}

First observedOct 25, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context that the terms are in English and include a PayPal pay_url, signaling a payment flow, but says nothing about freshness (whether terms change), caching, or size of the payload.

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?

A single front-loaded sentence that states the resource and then lists its contents; every item in the list carries information an agent needs to decide to call it.

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

Completeness4/5

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

With an output schema present and no parameters, the definition need only say what the tool is for, which it does. The one gap is behavioral: no note on whether the terms are static or can change between calls.

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?

Zero parameters and 100% schema coverage, so there is nothing for the description to compensate for; it correctly does not invent parameter discussion.

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 resource (the offer's terms) and enumerates its contents — answers, deliverables, price, hours, response times, pay_url, submission instructions — so an agent knows exactly what comes back. It does not explicitly distinguish itself from get_status, but the content list makes the boundary reasonably evident.

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 only implied: by listing 'how to submit a request' it hints that submit_request is the follow-on action, but it never says when to call this versus get_status or submit_request. No explicit when/when-not guidance is present.

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?