Skip to main content
Glama
Sign In

NumRadar

by app.numradar
OverviewDiscussionsAdmin

get_job_status

Read-only

Fetch progress counters for a bulk job, and optionally the per-number results. Free — a read uses no validations, but it does count against the account's per-minute request limit, so check about once a minute rather than in a loop: a job only moves at its plan's pace. Call with include_results once status is "completed".

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": {
      "job_id": "<job_id>"
    },
    "name": "get_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return (default 100).
job_idYesJob id returned by bulk_validate.
include_resultsNoInclude per-number results instead of counters only. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that reads consume no validations but do count against a per-minute request limit, and that job progress is gated by the plan's pace. That rate-limit and cost context is exactly the kind of behavioral detail an agent needs and cannot get from readOnlyHint/destructiveHint.

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?

Three sentences, front-loaded with purpose, followed by cost/rate behavior and then the conditional parameter hint. No filler; every clause carries operational information.

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 does describe the return shape (progress counters plus optional per-number results) and anchors job_id to bulk_validate. Minor gaps remain around error behavior for an unknown or expired job_id, keeping it at 4.

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 baseline is 3; the description adds real meaning by tying include_results to the completed status and implying limit governs the per-number results set. It does not explain limit bounds or default, but the schema already covers those.

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 ("Fetch progress counters for a bulk job") plus an optional extension ("per-number results"), which cleanly separates it from list_jobs and bulk_validate. An agent can tell this is the polling endpoint for a single job, not job creation or enumeration.

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

Usage Guidelines4/5

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

Gives explicit operational guidance: check about once a minute rather than in a loop, and call with include_results once status is "completed". It stops short of naming sibling alternatives (e.g. list_jobs) or stating when-not-to-use, so it lands at 4 rather than 5.

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

All NumRadar 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