Skip to main content
Glama
Sign In

mcp

by com.makehybrid
OverviewDiscussionsAdmin

MakeHybrid API: A one-hour link to the page where a member pastes their ChatWoot dashboard address and an administrator token: give it to them. The token never comes through here, and the connection appears on this API once they have finished.

complete_chatwoot_v1_connections_link
Destructive

A one-hour link to the page where a member pastes their ChatWoot dashboard address and an administrator token: give it to them. The token never comes through here, and the connection appears on this API once they have finished. -- MakeHybrid API plan, POST /chatwoot/v1/connections/link, group chatwoot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "complete_chatwoot_v1_connections_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON request body for POST /chatwoot/v1/connections/link.
queryNoOptional query-string parameters, e.g. {"limit":"20","cursor":"..."}. Values are coerced to strings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

It adds meaningful behavioral context beyond annotations: the link expires in one hour, the administrator token never comes through this tool, and the connection appears on the API only after the member finishes. However, it does not explain why destructiveHint=true applies to creating this link.

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 description is front-loaded and compact, immediately stating what the link is and how it is used. The trailing API plan metadata is slightly redundant but still useful for routing.

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 link-generation tool with no output schema, the description covers the important flow: one-hour expiry, token handling, and when the connection becomes visible. It does not address the destructiveHint annotation or explain how the optional body/query parameters should be used.

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 the body and query parameters are already documented in the schema. The description adds no additional semantics for those parameters, so the baseline score of 3 is appropriate.

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 action and resource: it provides a one-hour link where a member pastes their ChatWoot dashboard address and administrator token. It clearly explains what the link is for, though it does not explicitly distinguish this tool from sibling connection tools such as complete_chatwoot_v1_connections.

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?

The description gives clear usage context: give the link to a member so they can paste their dashboard address and admin token, and the token never passes through this API. It lacks explicit when-not-to-use guidance or direct alternatives among the many sibling connection-link tools.

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

All mcp 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