Skip to main content
Glama

Sellsy MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

Search invoices

sellsy_search_invoices
Read-onlyIdempotent

Search invoices by status (draft/due/payinprogress/paid/late/cancelled), number, date, currency, owner, or related company/individual/opportunity. Use it for unpaid or late invoices. Needs invoices.read.

Input Schema

NameRequiredDescriptionDefault
embedNoRelated objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"].
fieldNoOnly return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small.
limitNoRecords per page, 1-100 (default 25).
orderNoSort field: id, number, created, date, amount, due_date.
offsetNoPaging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous offset plus limit (0, 25, 50, ... for limit 25) until count is below limit.
filtersNoSearch filters as an object. Unknown keys are refused by Sellsy. Keys: status ["draft"|"due"|"payinprogress"|"paid"|"late"|"cancelled"], number (exact), currency, date {start,end} dates YYYY-MM-DD, created {start,end} ISO date-times, updated {start,end} ISO date-times, owners [staff ids], assigned_staff_ids [..], contacts [contact ids], related_objects [{type,id}] (type company|individual|opportunity), is_deposit (bool), is_progress_invoice (bool).
directionNoSort direction (default asc).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety behavior is covered. The description adds the important auth prerequisite (invoices.read), but does not add richer behavioral context such as return shape or pagination behavior.

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 two sentences, front-loads the search capability, and includes only useful details. Every sentence contributes either filter scope or the required permission.

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?

For a seven-parameter search tool with nested filters and no output schema, the description names the main search axes, gives a usage scenario, and states the required scope. The schema covers pagination and detailed filter semantics, though the description does not distinguish this tool from list_invoices or describe return shape.

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%, so the schema already fully documents the seven parameters, including nested filters and pagination. The description summarizes some filter keys but omits others and adds little syntax or meaning beyond what the schema provides.

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 gives a specific verb and resource and enumerates the main search dimensions, including status values and related object types. It is clear what the tool does, but it does not distinguish this search from the sibling sellsy_list_invoices or general sellsy_search.

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 explicitly says to use the tool for unpaid or late invoices and states the required invoices.read scope, which gives a clear usage context. It does not provide exclusions or name alternatives such as list_invoices for browsing all invoices.

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

All Sellsy MCP by usefulapi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources