Skip to main content
Glama

trello_connect

Connect to Trello via automatic browser authorization or manual token entry, then save the credentials so you can manage boards, lists, cards, and related data.

Instructions

Connect to Trello. mode=auto: opens the browser, the user clicks Allow, the token is captured and saved automatically. mode=manual: without token returns step-by-step instructions; with token verifies and saves it. Ask the user which mode they prefer before calling.

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": {
      "mode": "<mode>"
    },
    "name": "trello_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoISO 639-1 code of the language the user is writing in (e.g. en, ru, uk). Always pass it: server messages are returned in this language.
modeYes
forceNoreconnect even if already connected
tokenNomanual mode only: the token the user copied from Trello

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare a non-read-only, open-world, non-destructive operation; the description adds the real behavior — auto mode opens a browser and the user must click Allow, token is captured and saved automatically; manual mode returns instructions or verifies and saves a supplied token. Gaps remain around failure behavior, where the token is stored, and what is returned on success.

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?

Three compact sentences, front-loaded with the core action and then branching by mode, ending with a call-to-action constraint. No filler; the only slight weakness is opening with a vague verb phrase rather than stating explicitly that this is a token-based connection step.

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?

With no output schema, the description should cover return behavior but only describes the manual-without-token case (step-by-step instructions). It says nothing about what a successful auto-connect returns, what happens if the token is invalid, or how `force` interacts with an existing connection, leaving meaningful gaps for a connection tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75% and the undocumented parameter is the critical one — `mode` has an enum but no schema description, and the description fully defines both mode values. It also clarifies that `token` applies only to manual mode, which the schema states as well, so most added value is on the mode branch logic.

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 concrete operation — connecting to Trello and capturing/saving a token — and explains the two modes in operational terms. It is clear enough to distinguish from all sibling tools, which are board/card operations, though the leading phrase 'Connect to Trello' alone is slightly ambiguous until the mode sentences are read.

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?

It gives a direct procedural guideline: 'Ask the user which mode they prefer before calling,' which is unusual and helpful. It does not explain when to choose auto vs manual (e.g., no browser available) or state that this must run before other Trello tools, but the context makes the prerequisite fairly obvious.

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