Skip to main content
Glama

assign_member

Assign a board member to a Trello card by providing card and member IDs; get member IDs from get_board_members first.

Instructions

Assign a board member to a card (get ids from get_board_members).

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": {
      "cardId": "<cardId>",
      "memberId": "<memberId>"
    },
    "name": "assign_member"
  }
}

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.
cardIdYes
memberIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is known. Beyond that the description adds no behavioral detail: it does not say whether reassignment replaces an existing member, whether repeated calls are idempotent, or how failures surface. For a mutation tool this is a thin disclosure layer.

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?

A single short sentence with the action front-loaded and the id-sourcing hint in parentheses; nothing is padded. It is efficient, though the parenthetical could have been phrased as a clearer prerequisite clause.

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 annotations covering the safety profile and no output schema required, the main missing piece is mutation semantics (already-assigned behavior, replacing vs adding). Adequate to invoke correctly, incomplete for predicting the effect of the call.

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 only 33% — cardId and memberId have no field-level descriptions in the schema. The description partially compensates by telling the agent where memberId values come from (get_board_members) and implying cardId identifies the target card, but it never mentions the lang parameter or the accepted id format, so the gap is narrowed rather than closed.

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 pairs a specific verb with a specific resource and target: 'Assign a board member to a card'. An agent can distinguish this from unassign_member and remove_member_from_board purely on the verb. It stops short of explicitly naming the sibling it must not be confused with, which keeps it out of 5 territory.

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?

It gives one useful prerequisite — obtain ids from get_board_members — which tells the agent how to prepare inputs. But it says nothing about when to prefer this over unassign_member, what happens if the member is already assigned, or any permission/locale prerequisites, so usage context is only partially covered.

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