tiny_get_invoice
Read-onlyIdempotent
Detalha uma nota fiscal pelo id (nota.fiscal.obter.php).
Bulk support: accepts ids for batched execution.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| ids | No | ||
| account | No |
Tiny (Olist Tiny)
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds the bulk execution capability, which is a behavioral trait beyond annotations. It doesn't describe return format or error handling, but given annotations, this is acceptable.
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 short sentences, front-loaded with purpose, then bulk support. Minimal waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple getter with safety annotations, the description covers purpose and bulk capability. However, it omits the account parameter and has no examples or return info. Given schema coverage 0%, it could be more complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has no descriptions, so the description must explain params. It explains 'id' and 'ids' but not 'account'. Thus it partially compensates for the lack of schema descriptions.
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 uses the verb 'Detalha' (details) and specifies the resource 'nota fiscal' (invoice) by id, clearly distinguishing from list_invoices which would retrieve multiple. The reference to the underlying script adds specificity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It mentions bulk support indicating when to use it for batch retrieval, but doesn't compare to list_invoices or state when not to use it. No explicit alternatives are mentioned.
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.