GLØDI

Search treatments

search_treatments

Read-onlyIdempotent

Search treatments in Norwegian and English at once; spelling mistakes and compound words are handled. Each result has its treatment_id, category path, price from-to, offer price, duration, clinic count and, with near or place, the nearest clinics. Filter by category, body_area or skin_concern (browse_site lists them). Treatments no clinic can book now are left out unless include_unbookable is true. Without a match: suggestions and categories.

Input Schema

Name	Required	Description	Default
`near`	No	A position. It wins over place.
`page`	No
`place`	No	A town or place name ("Asker", "Lierskogen") or a four-digit postal code ("3420").
`query`	No	Treatment words in Norwegian or English. Leave empty to browse.
`locale`	No	Answer language: nb (Norwegian) or en.	nb
`category`	No	A category slug from browse_site, or its slug path ("ansikt/laser").
`on_offer`	No	Only treatments with an active offer.
`body_area`	No	A body area slug from browse_site.
`clinic_id`	No	The clinic_id find_clinics returns. Never build it from a name. A clinic site needs none.
`page_size`	No
`skin_concern`	No	A skin concern slug from browse_site.
`max_price_nok`	No	Only treatments with a price from at most this.
`include_unbookable`	No	Also treatments no clinic can book now.

Output Schema

Name	Required	Description
`next`	Yes
`count`	Yes
`place`	Yes
`results`	Yes
`complete`	Yes	false: some prices or bookability are still building.
`previous`	Yes
`categories`	Yes
`suggestions`	Yes
`corrected_query`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026
- addedOutput schema / properties / results / items / properties / offer / description
```
Added value: +"The live offer, null without one. Its prices are null when checkout sets the offer price."
```
First observedOct 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations cover read-only/idempotent safety. The description adds valuable behavior beyond that: bilingual matching with fuzzy/compound handling, default exclusion of unbookable treatments, the result field set (price from-to, offer price, duration, clinic count, nearest clinics with near/place), and fallback suggestions on no match.

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?

Three dense sentences, front-loaded with what the tool does and its differentiating search behavior. Slightly compressed (result field list is a run-on), but every clause earns its place.

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 13-param, 0-required search tool with an output schema, the description covers search semantics, filter sources, exclusion defaults, and the no-match path. Output schema covers returns; minor gaps around pagination behavior are acceptable.

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 85%, so the schema carries most parameter docs. The description nonetheless adds meaning: filters are category/body_area/skin_concern sourced from browse_site, and near/place enrich results with nearest clinics. Adds moderate value over 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?

States a specific verb+resource (search treatments) with distinguishing traits: bilingual search with typo and compound-word handling. This clearly separates it from browse_site (which lists categories) and get_treatment (single item lookup).

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?

Explains when results are excluded (unbookable unless include_unbookable) and where filter slugs come from (browse_site), and covers the no-match path. Lacks explicit guidance on when to use find_clinics or get_treatment instead, but usage context is clear.

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?