GLØDI

Price modules

price_modules

Read-onlyIdempotent

The monthly price of a set of modules (module_id from glodi_for_business) as GLØDI invoices it: each line, modules included at 0 kr, the base module added when the others need it, a public promo code, VAT, and an apply_url with these modules chosen.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "module_ids": "<module_ids>"
    },
    "name": "price_modules"
  }
}

Input Schema

Name	Required	Description	Default
`locale`	No	Answer language: nb (Norwegian) or en.	nb
`module_ids`	Yes	module_id values from glodi_for_business, for example booking and journal.
`promo_code`	No	A public promo code.

Output Schema

Name	Required	Description
`lines`	Yes
`notes`	Yes
`apply_url`	Yes	The clinic application with these modules chosen.
`module_ids`	Yes	The set that was priced.
`promo_valid`	Yes
`discount_months`	Yes	How many months the promo discount lasts.
`monthly_vat_nok`	Yes
`monthly_total_nok`	Yes	VAT excluded.
`monthly_discount_nok`	Yes
`monthly_subtotal_nok`	Yes
`monthly_total_with_vat_nok`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description still adds non-obvious behavior: zero-cost included modules, a base module automatically added when required by others, VAT handling, and an apply_url carrying the selection — all things an agent could not infer from the schema or annotations.

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?

One front-loaded sentence with the pricing scope first and the enumerated output components after the colon. The dash-separated list is dense but every clause carries information about what is returned; nothing is padding.

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 three-parameter, read-only pricing tool with an output schema, the description supplies the prerequisite tool, the notion of included/base modules, and the apply_url outcome. Return-value details are delegated to the output schema, which is appropriate, leaving only minor gaps around what happens with invalid module_ids.

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 coverage is 100% and all three parameters are documented in the schema itself, including locale, module_ids with a source hint, and promo_code. The description only restates the promo code as 'public' and the module source, adding little meaning beyond the structured fields, so the baseline 3 applies.

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?

The description names a specific resource (a set of modules) and a specific computed output (the monthly price as GLØDI invoices it), which is far more than a restatement of the name. The verb is stated nominally ('The monthly price of...') rather than as an action, but an agent can still tell exactly what this tool produces.

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?

There is no explicit when-to-use or when-not-to-use guidance relative to the many siblings, but the phrase '(module_id from glodi_for_business)' implicitly routes the agent through a prerequisite tool and indicates the input source. That is useful chaining context rather than a real usage policy.

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

All GLØDI tools Inspect

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

Need Help?