Skip to main content
Glama

get_request_status

Read-onlyIdempotent

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

NameRequiredDescriptionDefault
requestIdNoe.g. rowwcoz3zcm7

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses a polling rate limit, that organisation scoping comes implicitly from sign-in, and that a 'success false / No request with this requestId' reply can mean either a wrong id or cross-organisation access. The one gap is that the 'success' envelope shape is only implied by the error sentence rather than stated as the response contract.

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-loads the identity and trigger, then the call limit, then the status-to-action map; nothing is decorative. The single run-on paragraph with semicolon-chained status meanings is dense and would scan better as a list, which costs it a point.

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 return contract itself and defines every status value (received/building, completed, waiting_for_connection, needs_human, not_possible) with the concrete next action for each. Nothing an agent needs to act on the result is missing.

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 description adds real meaning: requestId must be the value returned by report_feedback and is scoped to the caller's organisation, which is why an unknown id can also mean a different org. That scoping insight is not in the schema.

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?

States a specific verb and resource (check a request filed with report_feedback) and names the originating sibling, plus the exact input that identifies the record. An agent can distinguish this from report_feedback and from the follow-up tools without opening any 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 triggering context (returning to unwired missing_capability work after a VIASOCKET-PENDING comment), hard limits (at most once an hour, never in a loop), and per-status branching that routes to list_app_actions or create_connection_link. When-to-use, when-not-to-use, and the alternative tools are all named.

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