Skip to main content
Glama

Fetch a saved scan's result

get_scan_result
Read-onlyIdempotent

For a signed-in user: the finished result for a scan on their account, in the same shape as price_item, once the sold comps have landed in the background. Call it with the account.scanId a photo price returned when that result said comps were still loading (about 20 seconds later), or to re-read any saved scan.

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": {
      "scan_id": "<scan_id>"
    },
    "name": "get_scan_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
costNoWhat the user would pay, in the scan's currency (price.currency), for a worth-it verdict.
scan_idYesThe account.scanId from a signed-in price_item, or the saved-scan link.

Output Schema

NameRequiredDescriptionDefault
itemNo
nextNo
textNo
compsNo
priceNo
sourceNo
accountNo
worthItNo
listPricesNo
marketplaceNo
unstructuredNoTrue: read `text`.
netAfterEbayFeesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "description": "The same fields as price_item's answer.",
      +  "properties": {
      +    "account": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {},
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "comps": {
      +      "additionalProperties": {},
      +      "properties": {},
      +      "type": "object"
      +    },
      +    "item": {
      +      "additionalProperties": {},
      +      "properties": {},
      +      "type": "object"
      +    },
      +    "listPrices": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {},
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "marketplace": {
      +      "additionalProperties": {},
      +      "properties": {},
      +      "type": "object"
      +    },
      +    "netAfterEbayFees": {
      +      "type": "number"
      +    },
      +    "next": {
      +      "additionalProperties": {},
      +      "properties": {},
      +      "type": "object"
      +    },
      +    "price": {
      +      "additionalProperties": {},
      +      "properties": {},
      +      "type": "object"
      +    },
      +    "source": {
      +      "additionalProperties": {},
      +      "properties": {},
      +      "type": "object"
      +    },
      +    "text": {
      +      "type": "string"
      +    },
      +    "unstructured": {
      +      "description": "True: read `text`.",
      +      "type": "boolean"
      +    },
      +    "worthIt": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {},
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / cost / description
      Previous value: -"What the user would pay, in USD, for a worth-it verdict."New value: +"What the user would pay, in the scan's currency (price.currency), for a worth-it verdict."
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, but the description adds genuinely new behavior: an authentication requirement and eventual consistency (the result only exists 'once the sold comps have landed in the background'). It stops short of saying what is returned if the result is still incomplete or unknown, which would have closed the loop.

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?

The authentication scope is front-loaded and every clause carries information (trigger, timing, return shape, reuse case). The second sentence is long and comma-chained, but it is dense rather than redundant.

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

Completeness5/5

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

With an output schema present, the description need not enumerate return fields and correctly offloads that by referencing price_item's shape. Auth scope, timing, and the ID source are all covered, leaving nothing an agent needs to invoke it correctly.

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 real provenance for scan_id ('the account.scanId a photo price returned' or the saved-scan link) that the schema cannot express. The second parameter, cost, is not discussed, though the schema documents it with bounds and a description.

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?

Names a specific resource (a saved scan's finished result) and constrains it to the signed-in user's own account, plus states the return shape mirrors price_item. That distinguishes it clearly from price_item (fresh pricing) and get_sold_comps (raw comps).

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

Usage Guidelines5/5

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

Gives explicit trigger conditions: call with the account.scanId returned when a photo price said comps were still loading, roughly 20 seconds later, or to re-read an existing saved scan. The alternative paths (wait-and-fetch vs. re-read) are both named with their conditions.

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