Skip to main content
Glama
Sign In
spoofzy

spoofzy

by spoofzy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Check a Spoofzy run

spoofzy_get_run
Read-onlyIdempotent

Check a Spoofzy run by ID to see its status, how many results are ready, and which files were saved. Optionally wait for completion before returning.

Instructions

Check a Spoofzy run by id: status, how many results are ready and which files were saved. Can wait for it to finish (wait_seconds). Runs started in this session are saved automatically when they finish; use spoofzy_download for other runs. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
run_idYesA run id from an earlier result (mjob_…, cc_…, api_… or batch_…).
workflow_idNoA workflow id (wa_…).
wait_secondsNoSeconds to wait for processing before returning (default from SPOOFZY_WAIT_SECONDS, normally 50). Unfinished runs keep processing and are saved when ready while this server runs; check them with spoofzy_get_run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, and the description is consistent with them ('Read-only'). Beyond that it discloses meaningful lifecycle behavior: the call can block for up to wait_seconds, unfinished runs keep processing server-side and get saved when ready, and only in-session runs are auto-saved. It does not describe the return payload shape or failure modes, which keeps it from a 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?

Four short sentences, front-loaded with the core purpose and return values, followed by the wait option and the sibling routing. Every clause carries distinct information with no repetition of the title or schema text.

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?

There is no output schema, and the description compensates by naming the key return fields (status, result count, saved files). It also covers the async/wait model and the cross-session download path. The only gap is that it never mentions the workflow_id parameter or how a workflow-scoped lookup differs, which the schema alone must carry.

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%, so run_id, workflow_id, and wait_seconds are already fully documented in the schema, including the wait default and id formats. The description only adds the framing that waiting lets the run finish; it contributes little parameter meaning beyond the structured fields, so the baseline applies.

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 (check a run by id) and enumerates exactly what comes back: status, number of ready results, and which files were saved. It also names the sibling (spoofzy_download) used for runs outside this session, so the agent can distinguish it from related tools without reading schemas.

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 a clear routing rule: runs started in this session are saved automatically, and other runs should go through spoofzy_download. It also explains the wait_seconds option as a way to block until finish. It stops short of stating explicit exclusions or when to prefer spoofzy_list_runs for discovery, but the primary alternative is named.

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

Deploy Server

Other Tools