Skip to main content
Glama
Sign In
Atlassian Trello MCP Server

Atlassian Trello MCP Server

by agrath
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

trello_get_checklist_field

Retrieve the name or position of a checklist by providing its ID. Use this to extract specific checklist details without fetching the entire object.

Instructions

Get a specific field (name or pos) from a checklist.

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": {
      "checklistId": "<checklistId>",
      "field": "<field>"
    },
    "name": "trello_get_checklist_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoTrello API key (optional if TRELLO_API_KEY env var is set)
tokenNoTrello API token (optional if TRELLO_TOKEN env var is set)
checklistIdYesID of the checklist
fieldYesField to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It indicates a read operation ('get'), but does not state that it has no side effects, nor does it mention authentication requirements (though apiKey/token are in the schema). The description adds minimal behavioral context beyond the action itself.

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 a single sentence with no wasted words. It is appropriately concise for a simple getter tool, though it could be slightly expanded without losing conciseness.

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?

Given the tool's limited scope (retrieving one of two fields from a checklist), the description is minimally adequate. However, it lacks information about the return format or any output structure, which is not compensated by an output schema.

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%, with each parameter described. The description mentions the enum fields ('name', 'pos') which are already defined in the schema, so it adds no new semantic meaning. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly specifies 'Get a specific field (name or pos) from a checklist', which is a precise verb-resource pair. It distinguishes from sibling tools like trello_get_checklist (which retrieves the entire checklist) and trello_update_checklist_field (which modifies a field), making the intended use unambiguous.

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?

The description implies usage for retrieving a single field (name or pos) rather than the full checklist, but it does not explicitly state when to prefer this over trello_get_checklist or mention exclusionary criteria. No usage context or prerequisites are provided.

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

Deploy Server

Other Tools