Hands for Agents

Get status or answer operator

get_status

Returns the current status of a quote (id = quote_id) or a task (id = task_id): status, next_action (a short text on the next step), payments, updates, and messages with the operator (newest first, from operator or you). The answer is short: older_updates and older_messages count what is left out; full=true returns everything. With the optional message the call also stores a plain-text reply to the operator and e-mails it to the operator; message_sent is then true. While the operator has a message that has not been returned yet, the reply is not stored (message_sent: false) and the answer contains that message. The same text again within 10 minutes is ignored (duplicate_ignored: true). A status can change at any time; every call returns the state at that moment. test_mode true marks a test order: nothing is paid or invoiced.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	quote_id or task_id.
`full`	No	true returns the complete answer.
`message`	No	Optional reply to the operator: plain text, 1-2000 characters. Without it the call is a plain status check.
`access_token`	Yes	Access token of the quote and its task, issued with the quote.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 2, 2026

changedInput schema / properties / access_token / description

Previous value: -"Token returned by request_quote."New value: +"Access token of the quote and its task, issued with the quote."

changedInput schema / properties / full / description

Previous value: -"true: the complete answer."New value: +"true returns the complete answer."

changedInput schema / properties / message / description

Previous value: -"Optional reply to the operator: plain text, 1-2000 characters. Leave it out for a plain status check."New value: +"Optional reply to the operator: plain text, 1-2000 characters. Without it the call is a plain status check."

Changed1 schema field changedSep 28, 2026

addedInput schema / properties / full

Added value: +{
+  "default": false,
+  "description": "true: the complete answer.",
+  "type": "boolean"
+}

Changed1 schema field changedSep 28, 2026

changedInput schema / properties / message / description

Previous value: -"Optional. Your reply to the operator: plain text, 1-2000 characters, never HTML. It is stored in the message thread (shown in messages as from: agent) and e-mailed to the operator; the answer is the usual status, including this message. Leave it out for a plain status check. The same call twice sends two messages."New value: +"Optional reply to the operator: plain text, 1-2000 characters. Leave it out for a plain status check."

Changed1 schema field changedSep 28, 2026

addedInput schema / properties / message

Added value: +{
+  "description": "Optional. Your reply to the operator: plain text, 1-2000 characters, never HTML. It is stored in the message thread (shown in messages as from: agent) and e-mailed to the operator; the answer is the usual status, including this message. Leave it out for a plain status check. The same call twice sends two messages.",
+  "type": "string"
+}

Changed3 schema fields changedSep 23, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / access_token / description

Previous value: -"The access_token returned by request_quote."New value: +"Token returned by request_quote."

changedInput schema / properties / id / description

Previous value: -"The quote_id returned by request_quote."New value: +"quote_id or task_id."

Changed3 schema fields changedSep 23, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / access_token / description

Previous value: -"Token returned by request_quote."New value: +"The access_token returned by request_quote."

changedInput schema / properties / id / description

Previous value: -"quote_id or task_id."New value: +"The quote_id returned by request_quote."

Changed3 schema fields changedSep 23, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / access_token / description

Previous value: -"The access_token returned by request_quote."New value: +"Token returned by request_quote."

changedInput schema / properties / id / description

Previous value: -"The quote_id returned by request_quote."New value: +"quote_id or task_id."

Changed3 schema fields changedSep 23, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / access_token / description

Previous value: -"Token returned by request_quote."New value: +"The access_token returned by request_quote."

changedInput schema / properties / id / description

Previous value: -"quote_id or task_id."New value: +"The quote_id returned by request_quote."

Changed3 schema fields changedSep 23, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / access_token / description

Previous value: -"The access_token returned by request_quote."New value: +"Token returned by request_quote."

changedInput schema / properties / id / description

Previous value: -"The quote_id returned by request_quote."New value: +"quote_id or task_id."

Changed3 schema fields changedSep 23, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / access_token / description

Previous value: -"Token returned by request_quote."New value: +"The access_token returned by request_quote."

changedInput schema / properties / id / description

Previous value: -"quote_id or task_id."New value: +"The quote_id returned by request_quote."

Changed3 schema fields changedSep 23, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / access_token / description

Previous value: -"The access_token returned by request_quote."New value: +"Token returned by request_quote."

changedInput schema / properties / id / description

Previous value: -"The quote_id returned by request_quote."New value: +"quote_id or task_id."

Changed3 schema fields changedSep 23, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / access_token / description

Previous value: -"Token returned by request_quote."New value: +"The access_token returned by request_quote."

changedInput schema / properties / id / description

Previous value: -"quote_id or task_id."New value: +"The quote_id returned by request_quote."

Changed3 schema fields changedSep 23, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / access_token / description

Previous value: -"The access_token returned by request_quote."New value: +"Token returned by request_quote."

changedInput schema / properties / id / description

Previous value: -"The quote_id returned by request_quote."New value: +"quote_id or task_id."

First observedSep 19, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: the truncation/older_updates/older_messages semantics, full=true, the operator-message gate that defers storing a reply and flips message_sent, the 10-minute duplicate_ignored rule, and the volatility of status. It also implicitly explains why readOnlyHint=false and idempotentHint=false (the call can write and email a reply), so no contradiction.

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 purpose, then dense but relevant clauses about return shape and edge cases; each sentence carries information. It is somewhat long and run-on, which slightly hurts readability, but no sentence is wasted.

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 no output schema, the description carries the full burden and does so: it enumerates the returned fields, the truncation behavior, and the message_sent/duplicate_ignored/test_mode flags. An agent has everything needed to call and interpret it.

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%, giving a baseline of 3, and the description adds real meaning: id may be either a quote_id or task_id, full=true returns everything (with the older_* counts otherwise), and message triggers storage plus e-mail with the duplicate/queue caveats.

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?

States a specific verb+resource ('Returns the current status of a quote or a task') and enumerates what is returned (status, next_action, payments, updates, messages). It clearly distinguishes the two modes (status check vs. answering the operator), though it does not explicitly name any of the sibling tools.

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?

It explains the conditional use of the optional message ('Without it the call is a plain status check'), which implies when each mode applies. However, it offers no explicit guidance on when to call this versus confirm_delivery, create_task, list_services, or request_quote.

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

All Hands for Agents 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?