Skip to main content
Glama
Sign In

Supovia

by com.supovia.mcp
OverviewDiscussionsAdmin

Resolve or reopen a conversation

resolve_conversation
DestructiveIdempotent

Use this when someone wants to mark a customer conversation resolved or done, or reopen it. Returns the conversation id, resolved state and last edit time, and the operator dashboard updates live. Repeating the same state has no further effect. Not for replying to the customer.

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": {
      "conversationId": "<conversationId>"
    },
    "name": "resolve_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
resolvedNotrue to mark it resolved (the default), false to reopen it
conversationIdYesConversation to update

Output Schema

NameRequiredDescriptionDefault
statusYes
conversationYesOnly the id, resolved state and last edit time; null when not found. Customer identifiers, staff ids and organization ids are never returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / conversationId / description
      Previous value: -"Conversation id to mark resolved or reopened"New value: +"Conversation to update"
    • changedInput schema / properties / resolved / description
      Previous value: -"true marks the conversation resolved (default), false reopens"New value: +"true to mark it resolved (the default), false to reopen it"
    • addedOutput schema / properties / conversation / description
      Added value: +"Only the id, resolved state and last edit time; null when not found. Customer identifiers, staff ids and organization ids are never returned."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the idempotency sentence largely restates structured data. However, the description adds genuine non-schema context: the operator dashboard updates live (an external side effect) and it names the returned fields, giving the agent information annotations can't convey.

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?

Three short sentences, front-loaded with the trigger, then the effect, then the exclusion. No filler; every sentence earns its place.

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?

With an output schema present, return values need not be spelled out, and annotations carry the safety profile. The description still supplies trigger, exclusion, idempotency, and the live-dashboard side effect, so 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 both parameters are already documented in the schema, so the description needn't explain them. The text hints at the two-state nature ('resolved or reopen it') but adds no format or default details beyond what the schema provides; 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?

States a specific verb+resource pair (resolve/reopen a conversation) and explicitly carves out the adjacent sibling behavior with 'Not for replying to the customer,' which separates it from send_message. An agent can select it without opening the schema.

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 trigger ('when someone wants to mark a customer conversation resolved or done, or reopen it') and an explicit when-not ('Not for replying to the customer'). It stops short of naming the alternative tool to use instead, so it falls just under full marks.

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

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