Skip to main content
Glama

Check a request's status

get_request_status
Read-onlyIdempotent

Check where a request made through Daawid is: waiting for the user on Daawid's page, sent, delivered or opened. It never shows what the request says or who sent it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "runId": "<runId>"
    },
    "name": "get_request_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesThe request's ID ("run_…"), from the tool that made it.

Output Schema

NameRequiredDescriptionDefault
kindYes
entryYes
runIdYes
statusYes
updatedAtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds real value beyond them by disclosing output scope — status only, never the request text or sender identity — which sets expectations about what the agent can and cannot learn.

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?

Two short sentences, front-loaded with the action and its possible values, then a compact scope caveat. Nothing is redundant or padded.

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?

An output schema exists, so return structure needn't be explained, and the state enumeration plus scope caveat make the definition sufficient for correct invocation. Minor omissions such as whether status must be polled or is final are not addressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single runId parameter is already documented with its "run_…" format and origin. The description adds no additional parameter meaning, so baseline 3 applies.

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 and resource ("Check where a request ... is") and enumerates the four possible states, so an agent knows exactly what signal it returns. It is clearly distinct in kind from the request_* siblings, though it never names them explicitly.

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: the agent must infer that this is the follow-up call after a request_* tool returns a run ID. No when-not-to-use guidance or named alternatives are given, aside from the note that content/sender are out of scope.

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