Skip to main content
Glama
Sign In

mcp-server

by io.alterlab
OverviewDiscussionsAdmin

Job Status

alterlab_job
Read-onlyIdempotent

Look up a job by id. action=status (default) returns its status and result once finished; set wait (seconds) to hold the request until the job reaches a terminal status. action=explain returns the ordered per-stage timing breakdown, useful when a job was slow or failed. Job ids come from async scrape, crawl, batch and SERP responses.

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

Input Schema

NameRequiredDescriptionDefault
waitNostatus only: long-poll up to this many seconds
actionNostatus (default) or explain
job_idYesJob id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered for free. The description adds real behavioral detail beyond that: status returns the result once finished, wait holds the request until a terminal state, and explain yields an ordered per-stage timing breakdown. Nothing is said about expired/unknown job ids or error behavior, which keeps it below 5.

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 tight sentences, front-loaded with the core action, then mode semantics, then provenance of the id. Every clause carries information an agent needs; no filler or restatement of the title.

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 correctly carries the return-value story for both actions, which is what an agent needs to decide between polling and diagnosing. The missing piece is failure semantics (invalid or expired job id), a minor but real gap for a polling tool.

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, but the description adds meaning the schema lacks: action defaults to status, and wait is framed as blocking until a terminal status rather than merely a long-poll timeout. The only gap is that job_id is left as-is, matching 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 ('Look up a job by id') and then enumerates the two modes of operation, status and explain. It also names the sibling operations that produce job ids (scrape, crawl, batch, SERP), so an agent can place the tool precisely in the workflow without opening the schema.

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 selection guidance between the two actions: status for polling, explain for diagnosing slow or failed jobs, plus the condition for using wait (hold until a terminal status). It stops short of any when-not-to-use note or of pointing to alternative tools for job discovery, so it is a strong 4 rather than a 5.

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

All mcp-server 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