Skip to main content
Glama

Letzte Angebote

get_recent_offers
Read-onlyIdempotent

List the newest Angebote, Kostenvoranschläge and Auftragsbestätigungen of the connected facturo account with validity, totals, items, PDF links and when they were last emailed. Filter by client, document type or text. Use it to find the Angebot an Auftragsbestätigung confirms (source_offer_number) or to copy an earlier offer. Each row's status is open, accepted, declined, expired (past its validity) or issued (an Auftragsbestätigung). The PDF links are for the user to open.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10
searchNoMatches offer number, client name, reference lines or an item description
client_idNo
document_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real value: it defines the status vocabulary (open, accepted, declined, expired, issued), ties 'expired' to validity, and states that PDF links are for the user to open, which discourages the agent from trying to dereference them.

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?

The resource and returned fields are front-loaded, and each following sentence adds a distinct piece of information (filters, use cases, status semantics, PDF caution). It is dense but every sentence earns its place; no filler.

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?

With four optional parameters and no output schema, the description does the heavy lifting by enumerating return fields (validity, totals, items, PDF links, last emailed) and status values. Only the semantics of client_id and the default/maximum limit behavior are left to the schema, which is acceptable.

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 coverage is 50%: limit and search carry their own descriptions, while client_id and document_type are undocumented in the schema. The description only restates 'Filter by client, document type or text', mapping loosely to those parameters without adding format, semantics or enum meaning beyond the schema.

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 names a specific verb and resource ('List the newest Angebote, Kostenvoranschläge and Auftragsbestätigungen of the connected facturo account') and enumerates the returned fields, so the agent knows exactly what it retrieves. It distinguishes itself from get_recent_invoices implicitly through the document types, but never names that sibling, so sibling differentiation is left to inference.

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?

It gives concrete use cases: finding the Angebot that an Auftragsbestätigung confirms via source_offer_number, or copying an earlier offer. That is clear when-to-use guidance, but there are no explicit exclusions or pointers to alternative tools for invoice retrieval.

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