Skip to main content
Glama

create_board_card

Create a board card with automatic sequence numbering and markdown description support. Resolves kind and status from the board project type for consistent setup.

Instructions

Create a board card with safe defaults. Resolves kind/status from the board project type, increments the CARD-number sequence, and stores markdown description as inline Huly Markup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardYesa string that will be trimmed
titleYesa string that will be trimmed
descriptionNoBoard card description in markdown. Stored as inline Huly Markup.
kindNoa string that will be trimmed
statusNoa string that will be trimmed
assigneeNoAssignee Employee _id, exact email address, or exact person display name.
membersNoInitial card members. Each entry accepts Employee _id, exact email, or exact person display name.
locationNoOptional card location text.
coverNoCover settings for a board card.
startDateNoStart date timestamp in milliseconds.
dueDateNoDue date timestamp in milliseconds.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesThe successful tool result. The same value is also serialized as JSON in the text content for clients that do not read structuredContent.
warningsNoOptional agent-visible warnings about degraded result fidelity. Omitted when the server returned the documented happy-path payload.
Behavior4/5

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

The description adds useful behavioral context beyond annotations: auto-resolution of kind/status, sequence increment, and markdown conversion. However, it does not disclose error conditions, required permissions, or potential side effects like notifications, which would be expected for a creation tool.

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 two sentences, front-loaded with the main action, and every phrase conveys meaningful behavior. No redundant or vague 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?

Given the tool's complexity (11 parameters, nested objects, output schema), the description covers key behaviors like auto-resolution and markdown storage. However, it omits explanation of 'safe defaults', validation rules, or what happens with optional parameters like location and cover, leaving some gaps.

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

Parameters4/5

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

The description adds meaning for 'kind' and 'status' (auto-resolved) and clarifies that description is stored as Huly Markup. This goes beyond the schema's generic descriptions. For other parameters like 'cover' and 'dates', the schema provides adequate detail, so the description complements rather than duplicates.

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 explicitly states 'Create a board card' and details specific behaviors (resolving kind/status, incrementing sequence, storing markdown as Huly Markup), making the tool's purpose clear and distinct from siblings like 'create_card' or 'create_board'.

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 when to use this tool (for board cards with auto-resolution), but does not explicitly state when not to use it or provide alternatives. It lacks direct comparison to sibling tools like 'create_card' or 'update_board_card'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dearlordylord/huly-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server