agentcard

start_support_chat

Start a new support conversation and send the first message

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": {
      "message": "<message>"
    },
    "name": "start_support_chat"
  }
}

Input Schema

Name	Required	Description	Default
`message`	Yes	Your initial support message

Output Schema

Name	Required	Description	Default
`message`	Yes	Human-readable summary confirming the conversation was started.
`conversationId`	No	The ID of the newly created support conversation. Pass this to send_support_message or read_support_chat.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered, and the description stays consistent with it. It adds the useful fact that a message is sent as part of creation, but says nothing about whether a duplicate call opens a second conversation or whether a chat handle is returned for follow-up.

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?

One sentence, front-loaded with the primary action and with zero filler. Nothing is redundant or buried.

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 one-parameter tool with an output schema and full annotations, the definition covers the essentials. The only shortfall is the missing link to the sibling chat tools that would tell an agent how to continue the conversation after starting it.

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?

There is a single parameter with 100% schema description coverage, so the schema fully documents 'message'. The description's 'first message' phrasing matches the schema but adds no format, length, or content guidance beyond it, making the baseline 3 the right level.

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 gives a specific verb and resource ('Start a new support conversation') plus the additional action of sending the opening message. The words 'new' and 'first message' implicitly separate it from send_support_message and read_support_chat, though it never names them.

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?

Usage is only implied: an agent can infer this is the entry point before read_support_chat / send_support_message, but no explicit when-to-use, when-not-to-use, or alternative is stated. With three chat-related siblings in the toolset, this is a real gap.

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

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