Skip to main content
Glama

SteadyScrape Company Data

Get results of a longer run

get_results
Read-onlyIdempotent

Fetch the results of a company_profile, sites_using_technology or company_hiring_summary call that returned a run_id because it took longer than about two minutes. Returns the status while it is still running. Free: the original run is billed.

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_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesThe run_id from the earlier call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely new behavior: it may return an in-progress status rather than final data, so callers should expect to poll, and the retrieval itself is not billed while the original run is. It stops short of saying what happens after completion or whether run_ids expire, 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 short sentences, front-loaded with what is fetched and from which calls, then the in-progress return behavior, then the billing note. Every sentence carries distinct information with no filler.

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?

For a one-parameter polling tool with no output schema, the description covers the essential unknowns: when it applies, that it can return a non-final status, and that it is free. The main residual gap is the shape of a completed result, which is reasonable to leave to the tool's response rather than prose.

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 the single run_id parameter is already documented, so the schema carries the load. The description adds mild context by explaining where the run_id comes from (a timed-out async call), but no format, validity window, or error behavior beyond that, which matches the baseline for high-coverage schemas.

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 the results') and scopes it to exactly the three sibling tools whose calls can return a run_id. An agent can immediately tell this is the follow-up call for async jobs rather than a general results lookup.

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?

Explicitly gives the trigger condition: use it after company_profile, sites_using_technology, or company_hiring_summary returned a run_id because the call exceeded roughly two minutes. It does not state an explicit counter-case (e.g., what to do if the run_id is unknown/expired), but the usage context is clear enough that no inference about the primary path is required.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources