get_a2a_finder_jobs
List the user's recent A2A Finder scan jobs and their status. Call to find a job_id whose results to fetch.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Sorsa
by app.sorsa
TDQS
A4.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist. Description says it lists recent jobs and status, but doesn't detail ordering, limits, or side effects. Adequate for simple list tool but lacks depth.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, front-loaded with main function and follow-up purpose. No unnecessary words.
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?
Given no parameters or output schema, description covers purpose and usage adequately. Could mention more about what is returned (e.g., list with job_ids and statuses), but sufficient.
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?
No parameters in schema; baseline 4. No need for additional parameter info.
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 it lists recent A2A Finder scan jobs and their status, and specifies the purpose: to find a job_id. Distinguishes from siblings like start_a2a_finder_scan and get_a2a_finder_status.
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?
Description implies usage: call to get a job_id for fetching results, but does not name the next tool explicitly or provide when-not-to-use guidance.
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.
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.