Skip to main content
Glama

findings_list

Read-only

READ-ONLY. Problemi operativi rilevati OGNI GIORNO dal motore deterministico Vendooly sul Data-Hub (i numeri vengono dal motore dati, non dall'LLM). Regole: buybox_lost (Buy Box persa su ASIN che vendono), buybox_suppressed (Buy Box soppressa), stockout_risk (copertura reale FBA sotto soglia, merce in arrivo inclusa), ads_no_stock (product ad SP attiva su prodotti in esaurimento), negative_margin (SKU con netto negativo su 30g dal Settlement: fee+refund > incasso), listing_issue_99300 (bullet point soppressi da Amazon per claim promozionali/inviti al contatto/tempi di consegna: la listing spesso resta in vendita ma senza bullet; fix = riscrivere i bullet con update_listing e ricontrollare con get_listing included_data=issues). Ogni finding ha evidenza numerica (payload), severità (critical|high|medium) e — dove è sicura — proposed_action: la chiamata tool già preparata per correggere, da eseguire SOLO dopo approvazione esplicita dell'utente (mostra prima l'anteprima dove prevista). USALO come PRIMA MOSSA per "che problemi ho?", "cosa devo sistemare?", "controlla il mio account", e per il recap operativo quotidiano. Org-scoped: senza account_id copre tutti gli outpost; con account_id filtra quel venue. Default status=open.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax findings (default 50, cap 200)
statusNoFiltro stato (default open)
rule_keyNoSolo una regola
severityNoGravità: critical, high o medium.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / severity / description
      Added value: +"Gravità: critical, high o medium."
  2. Changed1 schema field changed
    • changedInput schema / properties / rule_key / enum
      Previous value: -[
      -  "buybox_lost",
      -  "buybox_suppressed",
      -  "stockout_risk",
      -  "ads_no_stock",
      -  "negative_margin"
      -]New value: +[
      +  "buybox_lost",
      +  "buybox_suppressed",
      +  "stockout_risk",
      +  "ads_no_stock",
      +  "negative_margin",
      +  "listing_issue_99300"
      +]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that ('READ-ONLY'). Beyond the annotations it adds real context: figures come from the deterministic data engine rather than the model, every finding carries numeric evidence (payload), a severity, and sometimes a pre-built corrective tool call that requires human approval. It does not describe pagination behavior or ordering of results, which keeps it just below the top.

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 read-only status and the core purpose are front-loaded, and the rule glossary is dense but each entry carries distinct decision value. It is long for a list tool and some of the remediation workflow detail (rewriting bullets and re-checking) belongs to the fix path rather than to invocation of this tool, but there is little pure filler.

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 no output schema, the description carries the burden of describing returns, and it does: evidence payload, severity levels, and optional proposed_action. It also covers the approval prerequisite and default filtering. The only material gap is the phantom account_id scoping parameter, which leaves the agent unsure how to filter to a single venue.

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 the baseline is 3, but the description genuinely adds meaning by explaining what each rule_key value detects (e.g. negative_margin = fee+refund exceed 30-day settlement revenue; stockout_risk includes inbound stock) and by restating the default status=open. However, it describes org scoping via an account_id parameter ('senza account_id copre tutti gli outpost') that does not exist in the input schema, which is a misleading detail for a caller trying to scope the query.

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?

The description opens with a specific verb and resource: findings are operational problems detected daily by the deterministic Vendooly engine on the Data-Hub, and it explicitly separates the data source from the LLM. It enumerates the six rule keys it can surface and names the sibling tools used for remediation (update_listing, get_listing), so an agent can distinguish it from the ads_* and list_* siblings without opening the schema.

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?

It states the exact trigger conditions in the user's own phrasing ('che problemi ho?', 'cosa devo sistemare?', 'controlla il mio account', daily operational recap) and frames itself as the PRIMA MOSSA. It also gives an explicit gate on the downstream action: proposed_action must be executed ONLY after explicit user approval, and a preview must be shown first where available.

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