Skip to main content
Glama
shukiv

blesta-mcp

by shukiv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get client services

get_client_services
Read-onlyIdempotent

Retrieve a customer's services (hosting, domains, add-ons) with status, package, renewal date and price. Filter by client, status, or fetch a single service by ID.

Instructions

List a customer's services (hosting accounts, domains, add-ons) with status, package/pricing, renewal date and price. Wraps Services.getList (paged, default status 'active') and, when include_renewal_price is set, Services.getRenewalPrice per service. Pass service_id instead of client_id to fetch a single service (Services.get), including module fields such as domain/username. Results are compacted by default; set full for the raw Blesta objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNoReturn complete Blesta service objects (package descriptions, email templates, meta). Default is a compact view.
pageNoResult page, starting at 1
statusNoStatus filter for listing: active, canceled, pending, suspended, in_review, scheduled_cancellation, allactive
client_idNoNumeric client ID whose services to list
service_idNoFetch this single service in full instead of listing
include_childrenNoInclude add-on (child) services in the list
include_renewal_priceNoAlso compute the next renewal price for each listed service (one extra API call per service)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses pagination, the 'active' default status, the extra API call per service when include_renewal_price is set, compact-by-default results, and the full raw-object mode. No hidden write behavior; no contradiction.

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?

Four dense sentences, each carrying distinct information: purpose, wrapper behavior/defaults, single-service mode, and output mode. Front-loaded with the main purpose; no filler.

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?

For a 7-parameter read-only tool with no output schema, it explains the returned shape (compact vs full), key fields, paging default, statuses, and the renewal-price cost. Nothing essential for selecting or invoking it correctly appears missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents every parameter. The description adds meaningful semantics for service_id vs client_id, the per-service cost of include_renewal_price, and what full changes in output shape, going beyond the bare schema.

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 names a specific verb and resource ('List a customer's services') and details the returned attributes (status, package/pricing, renewal date and price), which clearly differentiates it from sibling tools like search_services. The single-service variant is also stated explicitly.

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 usage context: pass client_id for a customer's service list or service_id to fetch one service, and notes the default status filter. It does not explicitly name alternative siblings or exclusion conditions, so it stops short of a 5.

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