Skip to main content
Glama
Sign In
nubiia-dev

MCP Holded

by nubiia-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_treasuries

Retrieve Holded treasury accounts with cursor pagination, field projection, and optional summary counts; note the balance field is a static opening figure, not a live cash position.

Instructions

List all treasury accounts (Holded API v2). Cursor-paginated: pass the previous response nextCursor as cursor. Response fields are snake_case; amounts are strings with decimal comma. WARNING: the balance field is a STATIC opening figure, not a live balance derived from transactions — do NOT rely on it for reconciliation or to compute the current cash position. Overlaps with list_bank_accounts/get_bank_account/create_bank_account (official treasury tools); consolidation planned for 2.1.

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", "balance"]). Reduces response size.
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\", \"balance\"]). Reduces response size by 70-90%. If not provided, returns default fields: id, name, balance"New value: +"Project only these fields per item (e.g. [\"id\", \"name\", \"balance\"]). 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

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well: it discloses cursor pagination, response field casing, amount formatting, and a critical warning that balance is a static opening figure rather than a live balance. These are exactly the behavioral traits an agent needs to avoid misuse.

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 front-loaded with the core purpose, then supplies pagination, response-format, and warning details in a compact sequence. Every sentence carries operational value, including the overlap and planned-consolidation note.

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

Completeness5/5

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

Given no annotations and no output schema, the description compensates by explaining pagination mechanics, response field formatting, amount formatting, and the important balance caveat. It is complete enough for an agent to call the tool correctly and interpret the result cautions.

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 documents all four optional parameters. The description adds useful cursor-pagination context and response-format details, but it does not add parameter-specific meaning beyond what the schema provides, so the baseline 3 is appropriate.

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?

The description states a specific verb and resource: 'List all treasury accounts'. It also distinguishes this listing operation from sibling get/create treasury tools and notes overlap with bank-account tools, so an agent can identify the tool's role without opening the schema.

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 clear context by naming overlapping alternatives (list_bank_accounts, get_bank_account, create_bank_account) and warns against using the balance field for reconciliation or cash-position calculations. It stops short of an explicit rule for when to choose this tool over those alternatives, but the warning and overlap note provide meaningful guidance.

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