Skip to main content
Glama
Sign In

lookup

by com.verirouteintel
OverviewDiscussionsAdmin

Bulk Job Status

vri_bulk_status
Read-onlyIdempotent

Status and progress of a VRI bulk lookup job by job id. When returned, show job_ui_url for browser progress and use results_tool with results_tool_arguments to read stored results. Links require authentication and do not guarantee results are ready.

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": "vri_bulk_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob id returned by vri_submit_job or the REST Jobs API

Output Schema

NameRequiredDescriptionDefault
job_idNo
statusNoJob state, e.g. RUNNING or COMPLETED
processedNoNumbers completed so far

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / job_id / description
      Previous value: -"Job id returned by vri_bulk_lookup or vri_submit_job"New value: +"Job id returned by vri_submit_job or the REST Jobs API"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real context: the job_ui_url is authenticated and does not guarantee results are ready yet. It does not cover polling cadence or what a terminal vs in-progress status looks like, which would have pushed it higher.

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?

Three short sentences with zero filler, leading with the operation and following with actionable follow-up steps. Slightly dense packing of auth caveat and routing in one sentence, but nothing is wasted.

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 values need no explanation, and the description still covers the post-call workflow (show job_ui_url, then read results via the results tool) and the auth/readiness caveats. An agent can call and follow up on this tool without further information.

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?

Only one parameter with 100% schema coverage, where the schema already says the job id comes from vri_submit_job or the REST Jobs API. The description adds 'by job id' but no extra format or sourcing detail beyond the schema, so the 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+resource+scope: 'Status and progress of a VRI bulk lookup job by job id.' The 'bulk lookup job' framing separates it from the single-lookup status tool, but it never names vri_operation_status, so the agent must infer that distinction.

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?

Routes the agent explicitly: use results_tool with results_tool_arguments to read stored results, and render job_ui_url for browser progress. It also sets expectations that links need auth and results may not be ready, though it does not state when to prefer this over other status tools.

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

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