Skip to main content
Glama
Sign In

CheckMyApp

by io.github.sorokinvj
OverviewDiscussionsAdmin

Get a check's status

get_check_status
Read-only

Status of a run: phase (queued/connecting/surface_scan/discovery/walking/anatomy/writing), terminal state (completed/partial/failed/canceled), verdict when done, and the latest progress events.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_check_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoAct in another of your teams, by its name or id (whoami lists them). Omitted: the key's own team
run_idYesRun id returned by start_check or latest_results, or the run's number as the verdict page shows it ("#332")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 safety is covered. The description earns credit for disclosing the return vocabulary — the phase ladder (queued through writing) and the terminal states (completed/partial/failed/canceled) — which is real behavioral context no annotation supplies. It stops short of saying whether progress events are bounded/paginated or how expensive repeated polling is.

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 with a colon enumerating exactly the four things returned. Zero filler and no redundant restatement of the title; the phase ladder is compressed inline rather than spelled out in prose.

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 no output schema, the description carries the burden of describing returns, and it does so adequately for a read-only status tool. The main omission is workflow context — how it relates to wait_for_run and whether it must be polled repeatedly — which matters given three sibling tools touch run outcomes.

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 description coverage is 100%, and both parameters are documented there, including the creative run_id alternative of a verdict-page number like "#332" and the cross-team 'team' parameter. The description adds no meaning beyond that, so the baseline of 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?

The description names a specific verb+resource (status of a run) and enumerates exactly what the response carries: phase, terminal state, verdict, and latest progress events. It is clear what the tool does, but it never names the sibling it is not — wait_for_run and latest_results overlap heavily with this territory and go unmentioned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all. The sibling list contains wait_for_run (blocking) and latest_results, yet the description gives no cue for choosing this poll-style check over waiting, or for calling it before get_verdict. The agent must infer the polling workflow from names alone.

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

All CheckMyApp toolsInspect
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