Skip to main content
Glama

Browse the site

browse_site
Read-onlyIdempotent

The map of everything public here: every list page with its count, and the treatment categories, body areas and skin concerns with their slugs, for vague needs ("pigmentering", "acne"). Also the contact facts. GLØDI's own offer for clinics is glodi_for_business.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browse_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoAnswer language: nb (Norwegian) or en.nb

Output Schema

NameRequiredDescriptionDefault
nameYes
scopeYesglodi or clinic.
contactYes
sectionsYes
clinic_idYes
body_areasYes
categoriesYes
skin_concernsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / business_plans
      Removed value: -{
      -  "additionalProperties": false,
      -  "description": "GLØDI's software plans for clinics (glodi.no only).",
      -  "properties": {
      -    "add_ons": {
      -      "items": {
      -        "additionalProperties": false,
      -        "properties": {
      -          "contact_only": {
      -            "type": "boolean"
      -          },
      -          "description": {
      -            "type": "string"
      -          },
      -          "features": {
      -            "items": {
      -              "type": "string"
      -            },
      -            "type": "array"
      -          },
      -          "monthly_price_nok": {
      -            "description": "VAT excluded.",
      -            "type": [
      -              "number",
      -              "null"
      -            ]
      -          },
      -          "name": {
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "name",
      -          "description",
      -          "monthly_price_nok",
      -          "features",
      -          "contact_only"
      -        ],
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "plans": {
      -      "items": {
      -        "additionalProperties": false,
      -        "properties": {
      -          "annual_price_nok": {
      -            "description": "VAT excluded.",
      -            "type": [
      -              "number",
      -              "null"
      -            ]
      -          },
      -          "description": {
      -            "type": "string"
      -          },
      -          "includes": {
      -            "items": {
      -              "type": "string"
      -            },
      -            "type": "array"
      -          },
      -          "monthly_price_nok": {
      -            "description": "VAT excluded.",
      -            "type": [
      -              "number",
      -              "null"
      -            ]
      -          },
      -          "name": {
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "name",
      -          "description",
      -          "monthly_price_nok",
      -          "annual_price_nok",
      -          "includes"
      -        ],
      -        "type": "object"
      -      },
      -      "type": "array"
      -    }
      -  },
      -  "required": [
      -    "plans",
      -    "add_ons"
      -  ],
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "scope",
      -  "clinic_id",
      -  "name",
      -  "sections",
      -  "categories",
      -  "body_areas",
      -  "skin_concerns",
      -  "contact",
      -  "business_plans"
      -]New value: +[
      +  "scope",
      +  "clinic_id",
      +  "name",
      +  "sections",
      +  "categories",
      +  "body_areas",
      +  "skin_concerns",
      +  "contact"
      +]
  2. First observed

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, closed-world behavior, so the bar is lower. The description still adds useful content beyond them: it delineates the scope ('everything public here'), enumerates the entity types and slugs returned, and includes contact facts. It doesn't mention freshness, size, or pagination, but as a static index that's a minor gap.

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?

The scope statement is front-loaded and every clause carries information. It is slightly telegraphic — 'Also the contact facts.' reads as an afterthought fragment — but there is 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?

With an output schema present, the description needn't explain return structure, and it covers when to reach for this tool and what domain it spans. The one thing an agent might still want — how this differs from reading a specific page — is implied rather than stated.

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 the only parameter, locale, is fully documented in the schema including the enum and default. The description adds nothing about locale (it doesn't say output language follows it or what strings get translated), so 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 states concretely what the tool returns: a map of public list pages with counts, plus treatment categories, body areas and skin concerns with their slugs, plus contact facts. That is a specific resource and scope. It doesn't explicitly distinguish itself from read_public_page or search_treatments, so it falls short of 5.

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?

It gives a real usage cue — 'for vague needs (“pigmentering”, “acne”)' — which implies this is the entry point when you lack a precise term. It names one alternative (glodi_for_business for the clinic offer), but never says when to prefer read_public_page or search_treatments over this, so the routing guidance is partial.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources