Skip to main content
Glama

web_link_create

Put an internal web service of one of the user's servers into the owner's Termalin cabinet as an 'internal site': a dashboard, admin panel or app that listens only inside that server's network (e.g. localhost:3000 on the server, or 10.0.0.5:8080 next to it). Termalin gives it its own address that only the owner can open, signed in to Termalin, through the server's Connector — nothing is exposed to the internet and no port is opened. Only private addresses are accepted. One site opens every page of an app: if the server already has a site on the same host:port, that one is returned (reused: true) instead of a new one, and open_url lands on the path you gave — so to send the user to another page or file of the same app, call this again with that path. To rename a site or point it at another port, use web_link_update rather than removing and adding. Returns the link's id, open_url and url. Give the user open_url to open the site (it signs them in to Termalin first). The .termal.ink address in url shows 'This link doesn't work' to anyone without a session, the owner included, until opened from the account. This tool does not open or read the site, and it can't give anyone else access: sharing with other people is done by the owner in the cabinet. An account can hold a limited number of internal sites; when it is reached, ask the owner to remove one (web_link_delete).

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": {
      "server": "<server>",
      "target": "<target>"
    },
    "name": "web_link_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoA short name for the owner's list, e.g. 'Grafana' (optional)
serverYesServer id (or exact name) from hosts_list — the server whose Connector reaches the site
targetYeshost:port of the site as seen from that server, e.g. localhost:3000 or 10.0.0.5:8080; a path may follow and is where open_url lands, e.g. 10.0.0.5:3000/grafana/ or localhost:8000/report.pdf
https_insideNoThe site itself speaks https (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / target / description
      Previous value: -"host:port of the site as seen from that server, e.g. localhost:3000 or 10.0.0.5:8080 (a path may follow, e.g. 10.0.0.5:3000/grafana/)"New value: +"host:port of the site as seen from that server, e.g. localhost:3000 or 10.0.0.5:8080; a path may follow and is where open_url lands, e.g. 10.0.0.5:3000/grafana/ or localhost:8000/report.pdf"
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes far beyond the annotations: nothing is exposed to the internet, no port is opened, only private addresses accepted, an existing site on the same host:port is returned with reused:true, and the <slug>.termal.ink URL shows an error to anyone without a session until opened from the account. Also states the tool does not open or read the site and cannot grant access to other people.

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-loaded with the purpose and dense with useful detail, but delivered as one long block of prose with no separation between the reuse rule, the return values, and the sharing/limit caveats. Every sentence earns its place, though scannability suffers.

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?

No output schema exists, yet the description names the return fields (id, open_url, url) and explains what to do with open_url. With four parameters, a mutation with no destructive side effects, and the reuse and quota behaviours covered, an agent has everything needed to call it correctly.

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 already 100%, but the description adds meaning the schema lacks — 'Only private addresses are accepted' constrains target, and the path-in-target behaviour determines where open_url lands. Minor gap: https_inside is not elaborated on beyond the schema's own note.

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 action and resource: putting an internal-only web service from one of the user's servers into the owner's Termalin cabinet as an 'internal site', with concrete examples (localhost:3000, 10.0.0.5:8080). This is clearly distinct from siblings like web_link_list, web_link_update and web_link_delete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing rules: reuse this call with another path to reach a different page of the same app, use web_link_update to rename or re-point rather than removing and adding, and use web_link_delete when the site limit is reached. Both when-to-use and named alternatives are given.

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.