Skip to main content
Glama

StoreTechScan — Ecommerce Tech Stack & ICP

Retrieve Saved Inspection Batch Results

get_inspection_results
Read-onlyIdempotent

Retrieve saved results for a previously submitted StoreTechScan job_id (from inspect_domains or web workspace) at 0 credit cost. Useful if a network connection dropped during an inspection.

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

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id (e.g. "job_...") returned by inspect_domains or check_credits.
platformNo
min_fit_scoreNo
b2b_wholesale_onlyNo
real_merchant_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: retrieval costs 0 credits and returns previously saved data rather than re-running the scan. It omits retention/persistence window and failure behavior for an invalid job_id.

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?

Two tight sentences, with the identity and cost of the operation front-loaded and the retrieval scenario following. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter read tool with no output schema, the description covers what the tool returns conceptually and its cost, which is the minimum an agent needs. The four undocumented optional parameters are a real gap, since their filtering semantics for a saved-result retrieval are entirely unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20%: job_id is documented in the schema, but platform, min_fit_score, b2b_wholesale_only, and real_merchant_only have no schema descriptions and get no mention in the description either. An agent cannot tell whether these act as filters applied to the saved results or are ignored, nor what platform values are accepted.

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 and resource ('Retrieve saved results for a previously submitted StoreTechScan job_id') and names the originating tool (inspect_domains), so an agent can tell it apart from the tool that produces the job. It stops short of explicitly contrasting with siblings like check_credits, but the resource is unambiguous.

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

Usage Guidelines3/5

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

Offers one scenario ('Useful if a network connection dropped during an inspection') plus the '0 credit cost' framing, which implicitly argues for retrieval over re-running an inspection. There is no explicit when-not guidance, no statement that this cannot start a new inspection, and no indication of what to do if the job_id is unknown or expired.

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