Skip to main content
Glama

Toggle Status

toggle_status_of_a_conversation
Destructive

Toggle Status. Set the status of the conversation to open, resolved or pending. While the account requires conversation attributes (see Get the required conversation attributes) and any is blank on the conversation, resolving it is refused with 422 and error set to missing_required_attributes; missing_attribute_keys lists the blank ones. Fill them in and resolve again. Bulk resolve skips such conversations instead of failing.

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": {
      "conversation_id": "<conversation_id>",
      "status": "<status>"
    },
    "name": "toggle_status_of_a_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesThe status of the conversation
conversation_idYesThe numeric ID of the conversation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the mutation profile is known. The description goes beyond that by disclosing the concrete failure mode: a 422 with `error` set to `missing_required_attributes` and `missing_attribute_keys` listing the blank fields, plus the divergence that bulk resolve skips rather than fails. What is still missing is whether changing status is reversible or what side effects (reopening, SLA timers) follow.

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 core operation is front-loaded and the error-handling detail is tightly written. The opening 'Toggle Status.' duplicates the title and earns nothing, which keeps it from a 5, but the remaining text is dense and purposeful.

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?

For a two-parameter mutation with no output schema, the definition covers the operation, the enum values, and the notable error path well enough to call it correctly. The main residual gap is side effects of each transition and permission requirements.

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%, so both parameters and the status enum are already documented in the schema, and the description only restates the enum values in prose. It adds no meaning about conversation_id semantics or status transitions beyond what the schema gives. 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 second sentence gives a specific verb plus resource plus the full value set: 'Set the status of the conversation to open, resolved or pending.' That is unambiguous about the operation. The leading 'Toggle Status.' merely restates the title and the description never distinguishes this from siblings like update_conversation, so it stops short of a 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 states a real usage condition — resolving can be refused with 422 when required attributes are blank, and bulk resolve skips those conversations — which tells the agent what to expect and what to do next. However, there is no guidance on when to pick this tool over update_conversation or assign_a_conversation, and no note on permissions or when reopening vs. resolving is appropriate.

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