Skip to main content
Glama
easor

easor

by Markku-hur

Search or get invoice

sales_get_invoice
Read-only

Retrieve or search sales invoices by organization number, invoice ID, status, contact, or date range to review billing details and payment status.

Instructions

Search or get invoice — GET /v1/{organizationNumber}/invoices [PublicGetInvoiceFIV1].

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organizationNumber": "<organizationNumber>"
    },
    "name": "sales_get_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
dateEndNo
dateTypeNo
sortTypeNo
contactIdNo
dateStartNo
invoiceIdNo
sortDirectNo
invoiceNumberNo
invoiceStatusNo
organizationNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

The annotations already establish that this is a non-destructive read-only operation, and the description's 'GET' wording is consistent with that. However, it adds no behavioral context beyond the annotations, such as pagination expectations, filter behavior, authentication needs, or how the endpoint handles the organization scope.

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?

The definition is short and front-loaded, but it is under-specified rather than efficiently concise. The internal '[PublicGetInvoiceFIV1]' token adds little value for an agent deciding how to call the tool, while the substantive parameter behavior is omitted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 12 parameters, no output schema, and no parameter descriptions, the description is far too thin. It gives the endpoint and operation name but omits the filtering, pagination, sorting, and direct-lookup behavior an agent would need to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are 12 parameters with 0% schema description coverage, and the description does not explain any of them. It does not clarify invoiceId versus invoiceNumber, dateStart/dateEnd versus dateType, invoiceStatus values, sorting, pagination, or the required organizationNumber beyond its presence in the path.

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 resource, invoice, and a retrieval operation via 'Search or get invoice' plus the GET endpoint. It is clear enough to distinguish the basic purpose, but the phrase 'search or get' does not clarify whether this is a list/search endpoint, a single-invoice lookup, or both.

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?

The description provides no guidance on when to use this tool versus alternatives, no preconditions, and no distinction between search and direct retrieval. It only repeats the operation through the endpoint, leaving selection context implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.