Skip to main content
Glama

trello_status

Read-only

Check Trello connection status to confirm API key and token setup, identify the auth mode, and review the recent connection log.

Instructions

Show Trello connection status: whether the API key and token are set, the auth mode, and the recent connection log.

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": "trello_status"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety behavior is covered. The description adds useful context by specifying that it reports API key/token presence, auth mode, and a recent connection log, though it does not elaborate on log contents or network behavior.

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?

The description is a single well-structured sentence that front-loads the main purpose and lists the key status fields without unnecessary wording.

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 status-check tool with one fully documented optional parameter and no output schema, the description gives an adequate overview of returned information. It could be slightly more complete by clarifying what the recent connection log contains, but no critical calling information is missing.

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 description coverage is 100%, and the single optional lang parameter is fully documented in the schema. The description adds no parameter meaning beyond the schema, 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 uses a specific verb ("Show") and resource ("Trello connection status") and names the key status details. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling trello_connect tool.

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 implied by the tool's diagnostic nature: check connection status. The description does not state when to use it versus trello_connect or other alternatives, nor does it provide explicit exclusions.

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