Supovia

Get support website details

get_website

Read-onlyIdempotent

Use this when someone asks about one of their Supovia websites by name or id, such as whether its AI customer agent is on. Returns the website's id, name, domain, AI-agent status and created and edited times, or not-found. Not for the help articles published on it.

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": {
      "idOrName": "<idOrName>"
    },
    "name": "get_website"
  }
}

Input Schema

Name	Required	Description	Default
`idOrName`	Yes	Website id, exact vanity id (its lowercase public address) or exact display name

Output Schema

Name	Required	Description	Default
`status`	Yes
`website`	Yes	Safe website metadata; null when not found. Organization ids, agent prompts, credentials, integration configuration and arbitrary metadata are never returned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 28, 2026

changedInput schema / properties / idOrName / description

Previous value: -"Website id, exact vanity ID, or exact display name"New value: +"Website id, exact vanity id (its lowercase public address) or exact display name"

addedOutput schema / properties / website / description

Added value: +"Safe website metadata; null when not found. Organization ids, agent prompts, credentials, integration configuration and arbitrary metadata are never returned."

Changed1 schema field changedSep 16, 2026

changedInput schema / properties / idOrName / description

Previous value: -"Website id or exact name"New value: +"Website id, exact vanity ID, or exact display name"

First observedAug 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the concrete return fields and the 'or not-found' outcome, which tells the agent a missing website is a normal result rather than an error. It does not mention auth or rate limits, so not a full 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both front-loaded: the usage trigger leads, followed by the return/negative-scope clause. No filler, and the example ('whether its AI customer agent is on') makes the intent immediately actionable.

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?

An output schema exists, so return shape need not be spelled out, yet the description still summarizes the key fields and the not-found case. For a single-parameter read tool with full annotation coverage, nothing an agent needs to call it correctly is missing.

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 description coverage is 100% and the single parameter is well documented there (id, vanity id, or exact display name). The description echoes 'by name or id' but adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

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?

The description gives a specific verb+resource ('get ... website details') and names the exact lookup keys (name or id). It also explicitly carves out what this tool is not for ('Not for the help articles published on it'), which cleanly separates it from get_document.

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?

It states the triggering situation ('when someone asks about one of their Supovia websites by name or id'), gives a concrete example intent ('whether its AI customer agent is on'), and provides an explicit exclusion pointing at the sibling domain (help articles). Both when-to-use and when-not-to-use are covered.

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

All Supovia 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?