Nodiom Cloud

Add a card

board_add_card

Adds a card to a board, with a permanent id. Returns the card's id. Goes into the first column unless you name another. Use this to hand work to another agent or to a person.

Input Schema

Name	Required	Description
`agent`	No	Who is adding it. Defaults to this API key's name.
`brief`	No	A short paragraph of context.
`title`	Yes	One line describing the work.
`column`	No	Which column. Defaults to the first.
`doc_id`	Yes	The board's document id, as returned by board_create or nodiom_list_docs.
`criteria`	No	Acceptance criteria, each a checkbox.

Output Schema

Name	Required	Description	Default
`column`	Yes
`card_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "card_id": {
+      "type": "string"
+    },
+    "column": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "card_id",
+    "column"
+  ],
+  "type": "object"
+}

First observedOct 18, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds the default-column behavior and the permanence of the card id, but says nothing about what a non-idempotent retry does (duplicate cards) or any permission requirements.

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?

Four short sentences, front-loaded with the core action and side effect before the usage hint. Each sentence carries information, though 'with a permanent id' and 'Returns the card's id' partially overlap.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With full schema coverage, rich annotations, and an output schema covering the return value, the description supplies everything else an agent needs: default placement, the creation side effect, and the intended hand-off use case.

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%, so all six parameters (including title, brief, criteria, agent) are already documented in the schema. The description's only parameter-level contribution, the default column behavior, essentially restates the schema's own column description, so the baseline 3 applies.

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 opens with a specific verb and resource ('Adds a card to a board') and states the side effect (permanent id) plus the return value. This cleanly separates it from siblings like board_create (makes the board), board_update_card, and board_move_card.

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 concrete usage context ('hand work to another agent or to a person') and clarifies default placement behavior. It does not name alternative tools or when-not-to-use this one, so it stops short of full routing guidance.

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

All Nodiom Cloud tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.