get_request_status
Check a request you filed with report_feedback, by the requestId it returned. Use it for a missing app, action, trigger or field (kind missing_capability) you left unwired with a VIASOCKET-PENDING comment: call it when you come back to that work, at most once an hour, never in a loop. Body { "requestId": "row..." }; the org comes from the sign-in. Answers status, message and next (what to do now): received or building (keep it unwired, check later); completed (it is public: call list_app_actions with its serviceId, no need to search for it, use its actionIds, wire the pending part and test it); waiting_for_connection (viaSocket built it but could not connect it with its own account, so it is published privately in your organisation: call create_connection_link with its serviceId, give the link to the person you work for, and once they have connected wire and test it as for completed); needs_human (a person at viaSocket is handling it; message says what is needed; tell the person you work for); not_possible (message says why; leave it unwired and tell them). success false with 'No request with this requestId' means the id is wrong or belongs to another organisation.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_request_status"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| requestId | No | e.g. rowwcoz3zcm7 |