Skip to main content
Glama
Sign In

mcp

by com.makehybrid
OverviewDiscussionsAdmin

MakeHybrid API: The inboxes of that ChatWoot account, with the inbox_id a conversation names and what channel each one is.

complete_chatwoot_v1_connections_inboxes
Read-onlyIdempotent

The inboxes of that ChatWoot account, with the inbox_id a conversation names and what channel each one is. -- MakeHybrid API plan, GET /chatwoot/v1/connections/{connection_id}/inboxes, group chatwoot.

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": {
      "connection_id": "<connection_id>"
    },
    "name": "complete_chatwoot_v1_connections_inboxes"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional query-string parameters, e.g. {"limit":"20","cursor":"..."}. Values are coerced to strings.
connection_idYesValue for the {connection_id} segment of /chatwoot/v1/connections/{connection_id}/inboxes. Required; pass it raw (it is URL-escaped for you).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds modest value by stating the GET endpoint and the shape of returned data (inbox_id, channel), but gives no detail on pagination, ordering, or error behavior.

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?

It is short and front-loads the resource description before the endpoint metadata. The second clause is awkwardly worded, but overall the text wastes little space.

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 simple read-only GET list with no output schema, the description does tell the agent what the response contains (inbox_id and channel) and the endpoint. Combined with a fully covered schema, this is reasonably complete, though it omits pagination behavior implied by the query param.

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 the required connection_id and optional query object are fully documented in the schema. The description adds nothing beyond the schema about parameter semantics; the baseline 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 names a specific resource, 'the inboxes of that ChatWoot account,' and clarifies the returned fields (inbox_id and channel). An agent can tell this is a ChatWoot inbox listing, distinct from the conversations sibling, though the awkward noun-phrase phrasing ('the inbox_id a conversation names') and lack of a clear verb keep it from 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named for comparison. The only usage signals are the endpoint path and 'group chatwoot,' which are routing metadata rather than selection guidance.

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