Skip to main content
Glama

Sorsa

by app.sorsa

start_a2a_finder_scan

Start an A2A Finder scan: check a list of ASINs for profitable Amazon-to-Amazon flips across marketplaces (buy on one Amazon country, sell on another). Up to 100 ASINs. Optional countries = list of country codes to compare (e.g. ["UK","DE","FR"]); defaults to all. Uses the shared Keepa scan key (counts against the user's daily scan credits). Returns a job_id — poll get_a2a_finder_status(job_id) for results. Premium feature.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asinsYes
countriesNo

TDQS

A4.3/5.0
Behavior4/5

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

Discloses key behaviors: uses shared Keepa scan key, counts against daily scan credits, returns a job_id for async polling, and is a premium feature. No annotations provided, so description carries full burden.

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?

Six sentences, no fluff, front-loaded with purpose. Could be slightly more structured but efficient.

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?

Covers all key aspects: purpose, parameters, limits, credit usage, async nature, polling. Lacks details on output format but no output schema exists.

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?

Adds meaning beyond schema: explains asins are limited to 100, countries are optional with examples and default. Schema has 0% description coverage, so this is valuable.

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?

Description clearly states the tool starts an A2A Finder scan for profitable Amazon-to-Amazon flips, with specific details on ASINs, marketplaces, and optional country filter. It distinguishes from siblings like start_reverse_source_scan.

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?

Explicitly states when to use (checking a list of ASINs for flips) and mentions credit usage and polling. Does not explicitly exclude alternatives like analyse_product for single ASIN analysis.

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

All Sorsa toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool targets a distinct data type or action (e.g., product analysis, deal types, FBA operations). Even similar-sounding tools like get_deal_results and get_oa_deals are clearly separated by domain (A2A vs OA) in descriptions. No significant overlap.

Naming Consistency5/5

All tools follow a clear verb_noun pattern with underscores (e.g., analyse_product, create_deal_task, get_credits). The consistent 'get_' prefix for retrieval tools and varied but predictable action verbs make the set easy to navigate.

Tool Count4/5

At 37 tools, the set is large but covers a broad Amazon seller ecosystem (research, sourcing, FBA, deals, monitoring). Each tool serves a distinct purpose, and the count reflects the domain's complexity without being bloated.

Completeness5/5

The tool surface covers all major seller workflows: product analysis, profit calculation, sourcing, deal discovery, storefront monitoring, FBA operations, purchase tracking, price alerts, and reconciliation. No obvious gaps for core tasks.

Resources