Skip to main content
Glama
Sign In

ChatCut

by io.chatcut
OverviewDiscussionsAdmin

connect_plugin

Show the native Dropbox or X Connect action in the targeted Web project. The user starts OAuth and grants Agent access there, then returns to this same task. This does not connect, upload or publish automatically. No cross-platform settings window.

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": {
      "provider": "<provider>"
    },
    "name": "connect_plugin"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYes
projectIdNoProject for this call (full ID or unambiguous prefix). Explicit-timeline calls never change the target of later calls; legacy project selection applies otherwise.
timelineIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Adds real context beyond the annotations: the tool only surfaces a UI action, the human completes OAuth outside the agent's control, and nothing is connected, uploaded or published automatically. This is consistent with readOnlyHint=false and destructiveHint=false — a user-mediated write-adjacent action — and the explicit 'does not connect automatically' warning prevents a false expectation of a completed integration.

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?

Front-loaded with the action and provider options, followed by the user-side flow and the two clarifying negatives. Four short sentences, no filler, though 'No cross-platform settings window' is a slightly cryptic fragment that costs a beat of parsing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the OAuth handoff and the 'not automatic' framing well for a three-parameter tool with no output schema. Gaps remain: timelineId semantics are absent, and it does not say what the agent should do after the user returns (for example, re-invoke or verify connection) or what the tool returns.

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?

With only 33% schema description coverage, the description must compensate, and it partially does: 'Dropbox or X' maps to the provider enum and 'targeted Web project' maps to projectId. The timelineId parameter gets no mention anywhere, so the compensation is incomplete.

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?

States a specific verb and resource: show the native Dropbox or X Connect action in the targeted Web project. That is clearly distinct from siblings like call_connector_tool or discover_connectors, though it never names those alternatives explicitly.

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 context is implied rather than stated: the user must start OAuth and grant Agent access, then return to this task. The negatives ('does not connect, upload or publish automatically', 'no cross-platform settings window') hint at when not to expect automation, but no sibling alternative is named for the case where a direct connector call is wanted.

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

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