holdmark · facts about online stores

Read one store's record

get_store

Read the full holdmark record for one store, by its domain. Figures are rounded against the merchant, order volume is published in bands rather than exact numbers, and every figure carries the period it covers and the source it came from. A fact with no data answers "not_measured" with its reason, never "no". If the domain is not in the registry you get a plain answer saying so, which is not a verdict about that store.

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": {
      "domain": "<domain>"
    },
    "name": "get_store"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	The store's domain, for example tienda.com. Without https:// and without www.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses rounding against the merchant, banded order volume, period and source metadata, the 'not_measured' semantics, and the not-in-registry behavior. It stops short of auth, rate-limit, or error-shape detail.

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 core purpose is front-loaded in the first clause, then behavioral caveats follow. Sentences are dense but each carries a distinct caveat (rounding, bands, not_measured, not-in-registry), so the length is largely earned.

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, so the description must convey return semantics, and it does: it explains rounding, banding, per-figure period/source attribution, and the not_measured convention. What is missing is any note on response shape or size, but the behavioral picture is otherwise sufficient for a single-parameter read.

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 schema already gives the format rule (no https://, no www) plus an example. The description adds no syntax beyond 'by its domain', so the baseline 3 applies.

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 ('Read the full holdmark record for one store') and pins the key ('by its domain'), which implicitly separates it from the sibling find_stores. It does not explicitly name the alternative, so it falls just short of a 5.

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

Usage Guidelines2/5

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

The text describes what you get back but never says when to call this versus find_stores or how_holdmark_works, nor any prerequisite for using the domain key. Usage is only inferable from 'by its domain'.

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

All holdmark · facts about online stores tools Inspect

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

Need Help?