scvd-store-MCP

Look in the Window

look_in_window

Read-onlyIdempotent

Browse the last five card pressings displayed in the shop window, each with its own detail page. Free and without an account, pick one with a window pick to move it to your binder.

Instructions

Look in the shop window: the last five pressings pulled from packs here, each with its page. Free, no account. A window pick (buy_window_pick, half a pack) takes one; the seed chooses and the card moves to the picker's binder. Completes when the result carries window and size.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "look_in_window"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`size`	Yes	How many packs the window shows.
`window`	Yes	Packs, newest first, each with its cards.
`pick_url`	No	The buy door for a window pick.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.1Sep 17, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuine behavior beyond that: no account or cost required, exactly five results, and a completion criterion ('Completes when the result carries window and size'). It does not describe failure or empty-window behavior.

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?

Three front-loaded sentences with no filler: purpose, cost, and the relationship to the paid action. The themed vocabulary ('pressings', 'packs', 'binder') is dense but consistent and each clause carries meaning.

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?

With an output schema present the description needn't detail return values, and with zero parameters there is no invocation ambiguity. Annotations carry the safety profile. What remains is themed jargon that an outside agent must infer, which keeps this short of complete.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The prose adds no parameter semantics because none exist.

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+resource (look in the shop window) and what it yields: 'the last five pressings pulled from packs here, each with its page.' That is concretely distinguishable from the sibling buy_window_pick, which it explicitly contrasts. It does not differentiate from the similarly named look_at_door, so it falls short of full sibling differentiation.

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 clear selection context ('Free, no account') and names the alternative action that consumes what this tool shows ('A window pick (buy_window_pick, half a pack) takes one'), establishing browse-vs-buy. It stops short of an explicit when-not-to-use rule, but the browsing context is unambiguous.

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