Skip to main content
Glama

search_supplier_fiscal_receipts

Search supplier fiscal receipts (bon fiscal furnizor).

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": "search_supplier_fiscal_receipts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-based (default 1)
stateNoFilter by document state: draft, open, closed, cancelled. The alias "issued" means open+closed (finalised — not a draft, not cancelled). Comma-separated for several (e.g. "open,closed"). Omit for all states.
date_toNoFilter document date <= this date (YYYY-MM-DD)
currencyNoFilter by currency code, e.g. "RON", "EUR"
per_pageNoResults per page (default 20, max 100)
date_fromNoFilter document date >= this date (YYYY-MM-DD)
supplier_nameNoFilter by supplier name (partial match)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about permissions, result ordering, or what a returned receipt record contains. The only behavior hinted at is that it is a search (read) operation, derived from the verb.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence, front-loaded and free of waste, but its brevity comes at the cost of under-specification rather than genuine efficiency.

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?

Seven filters, no annotations, and no output schema; an agent still cannot tell what a result record looks like or how results are ordered. The description should do more to compensate for the missing structured metadata.

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 description coverage is 100%, with each of the seven optional filters documented in the schema, including the non-obvious "issued" state alias and the comma-separated convention. The description adds no parameter meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (search) and resource (supplier fiscal receipts), reinforced by the Romanian domain term "bon fiscal furnizor," which disambiguates the document type. It does not, however, distinguish this from adjacent siblings like search_supplier_invoices or get_supplier_document.

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 indication of when to prefer this tool over the many sibling search_* tools or over get_supplier_document. The agent must infer usage purely from the tool name.

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