Skip to main content
Glama
Sign In
nubiia-dev

MCP Holded

by nubiia-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_services

Retrieve Holded services with cursor-based pagination and field filtering, or return only counts and metadata to reduce response size.

Instructions

List all services (Holded API v2). Cursor-paginated: pass the previous response nextCursor as cursor. Response fields are snake_case; amounts are strings with decimal comma. Supports field filtering to reduce response size.

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", "price", "tax"]). Reduces response size.
summaryNoReturn only count and pagination metadata without items (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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\", \"price\", \"tax\"]). Reduces response size by 70-90%. If not provided, returns default fields: id, name, price, tax"New value: +"Project only these fields per item (e.g. [\"id\", \"name\", \"price\", \"tax\"]). Reduces response size."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of items to return (default: 50, max: 500)"New value: +"Max items per page (server-paginated; use limit to control page size)"
    • removedInput schema / properties / page
      Removed value: -{
-  "description": "Page number for pagination (optional)",
-  "type": "number"
-}
  2. First observedv1.6.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses cursor-pagination semantics (use previous nextCursor), response formatting (snake_case fields, decimal-comma string amounts), and field-filtering to shrink payloads. It doesn't state rate limits or explicit read-only nature, but 'List' plus these details give solid behavioral context.

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?

Front-loads the action, then packs pagination, response format, and filtering into a few tight sentences. Dense but every clause contributes useful information; 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?

For a simple read-only list tool with no output schema, the description adequately covers return-shape quirks (snake_case, string amounts) and pagination. Minor gaps like default page size or what a 'service' record contains are 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 description coverage is 100%, so all four parameters (limit, cursor, fields, summary) are already documented. The description reinforces pagination and field filtering but adds little beyond the schema, meriting the baseline 3.

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?

States a specific verb and resource ('List all services') clearly, and the API version context is a bonus. It is distinguishable from get_service/create_service by the list verb, though it never explicitly names the CRUD siblings it differs from.

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?

The description explains how to paginate but not when to choose this tool over get_service, or any retrieval-context guidance. Usage is only implied by the 'List' verb, with no exclusions or alternative routing.

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