Supovia Customer Support

Show support overview

show_support_overview

Read-onlyIdempotent

Use this when someone wants a quick visual summary of their customer support. Returns a card with up to 20 websites (name, domain, AI agent on or off) and the 20 most recently active conversations (channel, open or resolved, times), optionally for one website. Not for complete open-conversation totals.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`websiteId`	No	Only this website; every website when absent

Output Schema

TableJSON Schema

Name	Required	Description
`websites`	Yes	Up to 20 websites: name, domain and AI-agent status only
`conversations`	Yes	The 20 most recently active conversations: channel, resolved state and timestamps. Customer identifiers, internal record ids, message bodies, prompts, credentials, internal notes, organization ids and arbitrary metadata are excluded.
`websitesHaveMore`	Yes
`conversationsHaveMore`	Yes
`openConversationCount`	Yes	Open conversations among the 20 shown, not the organization total

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 28, 2026

changedInput schema / properties / websiteId / description

Previous value: -"Optionally limit the overview to one organization-owned website"New value: +"Only this website; every website when absent"

addedOutput schema / properties / conversations / description

Added value: +"The 20 most recently active conversations: channel, resolved state and timestamps. Customer identifiers, internal record ids, message bodies, prompts, credentials, internal notes, organization ids and arbitrary metadata are excluded."

addedOutput schema / properties / openConversationCount / description

Added value: +"Open conversations among the 20 shown, not the organization total"

addedOutput schema / properties / websites / description

Added value: +"Up to 20 websites: name, domain and AI-agent status only"

Changed3 schema fields changedSep 17, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedAug 25, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful behavioral context beyond that: hard limits of 'up to 20 websites' and '20 most recently active conversations', plus the optional single-website scoping.

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?

Two sentences, front-loaded with the when-to-use condition and then the when-not/return detail. The return description is somewhat verbose ('AI agent on or off', 'channel, open or resolved, times'), but each detail aids routing rather than 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?

An output schema already exists so return values need not be explained, yet the description's card contents and the 20-item limits are still useful for tool selection. Complete for a read-only, single-parameter tool, with minor redundancy against the output schema.

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% for the single websiteId parameter, and the description's 'optionally for one website' merely restates the schema's 'Only this website; every website when absent'. Baseline 3 is appropriate when the schema does the heavy lifting.

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 a specific resource and scope: a 'quick visual summary of their customer support' returning a card of websites and recent conversations. It differentiates from siblings only via the negative 'Not for complete open-conversation totals', without naming the alternative (get_unresolved_conversation_counts).

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?

Gives a clear when-to-use condition ('when someone wants a quick visual summary of their customer support') and a when-not clause ('Not for complete open-conversation totals'). It stops short of naming the sibling to use instead, leaving that to inference.

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

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