Skip to main content
Glama

wintraits_seguir_ficha

Follow my Amazon listing every week. (Sigue mi ficha cada semana.)

Only call it when the user explicitly asks to follow the listing: it is their consent. Requires a free key (Authorization: Bearer). Each Monday we check whether the listing changed and, when it does, the user sees in their account how its Wintraits Scan Index moved and how its sales rank did against similar listings that did not change (correlation, not causation). Only the ASIN is stored, never the listing text. Returns {"seguida": true, "desde": "YYYY-MM-DD"}. The user can unfollow it from their account.

Args: asin: ASIN (10 characters) or Amazon product link. pais: country code when only the ASIN is given (default "ES"). lang: "es" (default) or "en".

Free and unlimited during the beta (until 2027-01-31). Gratis y sin límite durante la beta (hasta el 31-ene-2027).

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": {
      "asin": "<asin>"
    },
    "name": "wintraits_seguir_ficha"
  }
}

Input Schema

NameRequiredDescriptionDefault
asinYes
langNoes
paisNoES

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the free Bearer-key auth requirement, the weekly Monday evaluation cadence, what the user sees in their account, the correlation-not-causation caveat, storage limits (ASIN only, never listing text), and unfollow behavior. It even states the return payload shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core content is front-loaded and useful, but every Spanish parenthetical duplicates the English text, including the beta/pricing sentence, adding length without new information for an agent. Some pruning is warranted even though most sentences earn their place.

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?

For a consent-sensitive subscription tool with no annotations and no output schema, the definition covers auth, timing, privacy, the returned fields, cost during beta, and how to undo. An agent has everything needed to decide and call correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the Args block is doing essential work: it says asin accepts either a 10-character ASIN or a full product link, that pais is only needed when a bare ASIN is given and defaults to ES, and that lang is es/en with es default. That is meaning the bare schema does not provide.

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?

The description states a concrete verb and resource: follow a specific Amazon listing, re-checked every Monday. It is clearly not a one-off check like a sibling chequeo tool, but it never names a sibling or explicitly contrasts itself with them, so differentiation is inferred rather than stated.

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?

It gives an explicit gate: 'Only call it when the user explicitly asks to follow the listing: it is their consent.' That is a strong when-to-use condition with a clear when-not (do not call unprompted). It stops short of naming alternatives for non-subscription use cases.

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