tiny_list_sellers
Read-onlyIdempotent
Pesquisa vendedores (vendedores.pesquisa.php). Paginado. search busca por nome.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| search | No | ||
| account | No | ||
| filters | No |
Tiny (Olist Tiny)
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds behavior details beyond the annotations: pagination and that the 'search' parameter filters by name. This complements the readOnly/idempotent annotations well, though it does not describe output format or other potential side effects.
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?
The description is extremely concise, using only two short sentences. It avoids redundancy and clearly conveys the core purpose without unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity as a list operation, the description is incomplete. It omits details about pagination behavior, the meaning of 'account' and 'filters', and the expected response structure. The minimal info provided is not enough for a user to fully understand how to use the tool effectively.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one of four parameters ('search') is explained (searches by name). The parameters 'page', 'account', and 'filters' have no description in the schema or the description. With 0% schema coverage, this is a significant gap.
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 clearly states that the tool searches sellers ('Pesquisa vendedores') and provides the underlying function name. This is specific and distinct from sibling list tools for other resources (e.g., accounts, contacts).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives. It does not mention criteria like 'use for seller searches' or distinguish it from other list tools beyond the resource name. For a tool with many siblings, this is insufficient.
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
B3.1/5.0
Disambiguation2/5
The tiny_* tools are clearly distinct by resource and action, but the generic platform tools blur together: marketplace also handles report_bug, install/uninstall, token/connect links, and toolkit state, overlapping with authenticate, connect, report_bug, and toolkit_info. An agent could easily call marketplace for something a dedicated tool already covers, or confuse connect with authenticate.
Naming Consistency3/5
The Tiny ERP tools follow a clean verb_noun pattern (tiny_list_orders, tiny_get_product, tiny_create_contact), but the platform tools use short unprefixed verbs (authenticate, connect, marketplace, report_bug, show_version, toolkit_info). Two internally consistent naming schemes coexist, so the overall set feels mixed rather than chaotic.
Tool Count3/5
At 20 tools, the count is borderline heavy and mixes two distinct concerns: Tiny ERP operations and mcp.ai platform administration. The ERP tools are each reasonably scoped, but the generic tools could likely be consolidated, especially marketplace, which already absorbs several capabilities.
Completeness2/5
The ERP surface is heavily read-oriented: contacts, orders, invoices, products, payables, and receivables all support list/get, but only contacts have a create operation. There are no update/delete operations for any entity and no way to create orders, invoices, or products, which creates significant dead ends for real business workflows.