Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create Card Builder card

card_builder_create_card

Create a new Card Builder card from a DocumentData config, returning its new id. Use when saving a built card; edit existing cards with the update tool.

Instructions

Create a new Card Builder card from a DocumentData config.

Sends config and the metadata fields to card_builder/cards/create, which assigns a new id server-side (confirmed in upstream storage.py: every create path generates a fresh uuid4) — repeating this call with identical arguments creates a second, distinct card rather than updating the first.

Use when: saving a card built with card_builder_build_from_recipe or card_builder_make_template_card's underlying recipe. Not for: changing an existing card — use card_builder_update_card. Returns: the created card dict, including its new id. Limits: run card_builder_validate_config on config first; this tool does not validate the block tree before sending it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name for the new card, e.g. 'AC Salon'.
tagsNoFreeform tags for filtering in the Card Builder UI. Omit for no tags.
authorNoAuthor name to store on the card. Empty string if omitted.
configYesFull DocumentData v3 block tree (version/rootId/slots/blocks). Build it with `card_builder_build_from_recipe` rather than hand-writing it.
categoriesNoCategory labels (e.g. domain names) for the Card Builder UI. Omit for none.
descriptionNoFree-text card description. Empty string if omitted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.25.1
    • addedInput schema / properties / author / description
      Added value: +"Author name to store on the card. Empty string if omitted."
    • addedInput schema / properties / categories / description
      Added value: +"Category labels (e.g. domain names) for the Card Builder UI. Omit for none."
    • addedInput schema / properties / config / description
      Added value: +"Full DocumentData v3 block tree (version/rootId/slots/blocks). Build it with `card_builder_build_from_recipe` rather than hand-writing it."
    • addedInput schema / properties / description / description
      Added value: +"Free-text card description. Empty string if omitted."
    • addedInput schema / properties / name / description
      Added value: +"Display name for the new card, e.g. 'AC Salon'."
    • addedInput schema / properties / tags / description
      Added value: +"Freeform tags for filtering in the Card Builder UI. Omit for no tags."
  2. Addedv0.18.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false, but the description adds concrete consequences: every create path generates a fresh uuid4, so repeating with identical arguments creates a second distinct card rather than updating. It also discloses that the block tree is not validated before sending and that the created card dict including the new id is returned.

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 front-loaded with the core action, then cleanly segmented into Use when, Not for, Returns, and Limits. Every sentence adds operational value with no repetition or filler.

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?

Given the tool's mutation nature, full schema coverage, output schema, and annotations, the description is complete. It covers creation semantics, non-idempotency, prerequisite validation, routing to siblings, and return behavior, leaving no critical gap for correct invocation.

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 are already documented in the schema. The description adds only high-level framing ('sends config and the metadata fields') without new syntax, format, or constraint details beyond what the schema provides. Baseline 3 is appropriate when 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 states a specific verb and resource ('Create a new Card Builder card from a DocumentData config') and distinguishes the tool from siblings by naming update_card, build_from_recipe, make_template_card, and validate_config. An agent can identify the exact operation without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'Use when' and 'Not for' sections route the agent: use for saving a card built via recipes/templates, not for changing existing cards (use card_builder_update_card). It also states a prerequisite ('run card_builder_validate_config first'), covering when-not and alternatives.

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