Skip to main content
Glama
Sign In
nubiia-dev

MCP Holded

by nubiia-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_numbering_series

List the numbering series configured for a Holded document type, such as invoice, estimate, or purchase order. Use cursor pagination to retrieve every series page by page.

Instructions

List numbering series for a specific document type (Holded API v2). Cursor-paginated: pass the previous response nextCursor as cursor. Response fields are snake_case; amounts are strings with decimal comma.

Input Schema

NameRequiredDescriptionDefault
limitNoMax items per page (server-paginated; use limit to control page size)
cursorNoCursor from a previous response nextCursor
fieldsNoProject only these fields per item (e.g. ["id", "name", "prefix", "nextNumber"]). Reduces response size.
docTypeYesDocument type
summaryNoReturn only count and pagination metadata without items (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.0.3
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Cursor from a previous response nextCursor",
+  "type": "string"
+}
    • changedInput schema / properties / fields / description
      Previous value: -"Select specific fields to return (e.g., [\"id\", \"name\", \"prefix\", \"nextNumber\"]). Reduces response size by 70-90%. If not provided, returns default fields: id, name, prefix, nextNumber"New value: +"Project only these fields per item (e.g. [\"id\", \"name\", \"prefix\", \"nextNumber\"]). Reduces response size."
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max items per page (server-paginated; use limit to control page size)",
+  "type": "number"
+}
    • removedInput schema / properties / page
      Removed value: -{
-  "description": "Page number (starting from 1, default: 1)",
-  "type": "number"
-}
    • removedInput schema / properties / pageSize
      Removed value: -{
-  "description": "Number of items per page (default: 50, max: 500)",
-  "type": "number"
-}
    • changedInput schema / properties / summary / description
      Previous value: -"Return only total count and page count without items (default: false)"New value: +"Return only count and pagination metadata without items (default: false)"
  2. First observedv1.6.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, yet the description discloses two non-obvious behaviors: responses are snake_case and monetary amounts are strings with decimal comma. It does not cover auth requirements, error modes, or default page size behavior, which leaves some of the burden unmet.

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?

Three compact sentences, front-loaded with the purpose, then pagination, then response-format notes. Minor redundancy with the schema around cursor, but no wasted prose.

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?

A read-only list tool with a fully documented 5-parameter schema and no output schema; the description compensates for the missing return schema by flagging field naming and amount formatting. Only failure and permission behaviors are left unspecified.

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 all five parameters are already documented. The sentence about passing nextCursor as cursor echoes the schema's cursor description rather than adding format or edge-case detail.

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?

States a specific verb (List) and resource (numbering series) plus the scoping key (document type). Against siblings create_numbering_serie / update_numbering_serie / delete_numbering_serie, 'List' makes the read-vs-mutate distinction immediate.

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?

Explains pagination mechanics (pass previous nextCursor as cursor) but never says when to reach for this tool over the sibling numbering-serie tools or any alternative listing path. Usage is implied by the verb rather than stated.

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

Deploy Server

Other Tools