Skip to main content
Glama

UmbHost — Umbraco hosting storefront

by net.umbhost
OverviewDiscussionsAdmin

list_plans

List UmbHost's buyable plans with live prices, resources, config options, and add-ons: Umbraco hosting, email, and UmbCheckout licences (group 'Licence': billed annually, bought without a domain, with licenceDomains/licenceInstalls limits and add-ons that raise them). Optional group filter ('hosting', 'email' or 'licence'); omit for all. Optional ISO currency (GBP, EUR, USD, AUD); defaults to GBP. Prices exclude VAT.

Input Schema

NameRequiredDescriptionDefault
groupNoOnly return this group: 'hosting', 'email' or 'licence'. Omit for every group.
currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / group
      Added value: +{
+  "default": null,
+  "description": "Only return this group: 'hosting', 'email' or 'licence'. Omit for every group.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and adds useful context beyond a bare 'list': live pricing, VAT exclusion, annual billing for licence groups, no-domain requirement, and limit/add-on behaviour. It does not cover authentication or rate limits, but the core operational semantics are well disclosed.

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 core action and returned content before detailing licence specifics and parameters. The single dense sentence with parentheticals is information-rich and mostly efficient, though slightly run-on.

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?

With no output schema and no annotations, the description still explains what the tool returns (live prices, resources, config options, add-ons) and clarifies licence group semantics. It is complete enough for correct invocation, though it omits any pagination or authentication note.

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 50%, with the group parameter documented but currency undocumented in the schema. The description compensates by giving the currency options (GBP, EUR, USD, AUD) and default (GBP), while also restating the group filter and its omit behaviour, adding meaning beyond structured fields.

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 UmbHost's buyable plans') and enumerates the content type (prices, resources, config options, add-ons). It implicitly distinguishes from the sibling get_plan by being a list operation, but does not explicitly name or contrast with that alternative.

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?

Gives clear context for the optional group filter ('hosting', 'email' or 'licence'; omit for all) and currency defaults, which helps invocation. However, it offers no explicit when-to-use guidance against alternatives like get_plan, leaving the choice to inference.

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

All UmbHost — Umbraco hosting storefront 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