Skip to main content
Glama

invite_member

Invites a person to a Trello board by email and sends them an invitation email; use only when the user explicitly requests that exact invitation.

Instructions

Invite a person to a board by email. SIDE EFFECT: Trello sends an invitation email to that address, so only call this when the user explicitly asked for this exact invitation.

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": {
      "boardId": "<boardId>",
      "email": "<email>"
    },
    "name": "invite_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.
typeNonormal
emailYes
boardIdYes
fullNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, but the description adds real value by naming the concrete side effect: Trello sends an invitation email to the address. That is the single most important behavioral fact and it is stated up front. It does not mention permission requirements, whether an existing member is re-invited, or what the response contains, which keeps it below a 5.

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?

Two short sentences with no waste: the action comes first and the side-effect warning follows immediately. Nothing is repeated from the title or annotations.

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?

For a 5-parameter mutating tool with no output schema and a real external side effect, the definition covers the danger but omits the role parameter entirely, which materially changes what the invitation grants. An agent cannot tell from the description when to pass admin versus observer.

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

Parameters2/5

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

Schema description coverage is only 20%, so the description must carry the load, and it does not: the 'type' enum (normal/admin/observer), 'fullName', and 'lang' are never explained. It only echoes board and email, which the schema already names as required, so it adds no meaning beyond the input schema.

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 gives a specific verb and resource ('Invite a person to a board by email'), which is enough to distinguish it from assign_member, since inviting an unknown person by email is a different action than assigning an existing one. It does not explicitly name that sibling as an alternative, so it falls short of a 5.

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 an explicit when-not condition: call it only when the user explicitly asked for this exact invitation, which is exactly the guard an agent needs for an irreversible external side effect. It does not point at any alternative tool for the adjacent case of adding an already-existing member, leaving that inference to the agent.

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