Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Update Card Builder card

card_builder_update_card
Destructive

Update fields of an existing Card Builder card, such as name, config, tags, categories, or description, while leaving omitted fields unchanged.

Instructions

Update fields of an existing Card Builder card.

Sends only the parameters that are not omitted to card_builder/cards/update; every omitted parameter's prior value in storage is left untouched, but any parameter that is supplied (including config) fully replaces the previous value for that field with no way to recover it afterwards.

Use when: renaming a card, editing its config, or retagging it. Not for: creating a new card — use card_builder_create_card. Returns: the updated card dict as returned by the WebSocket command.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew display name. Omit to leave the current name unchanged.
tagsNoReplacement tag list. Omit to leave tags unchanged.
configNoNew DocumentData v3 block tree, replacing the whole config. Omit to keep the current config.
card_idYesId of the card to update, from card_builder_list_cards.
categoriesNoReplacement category list. Omit to leave categories unchanged.
descriptionNoNew description text. Omit to leave it unchanged.
skip_version_bumpNoIf true, do not bump the card's stored version counter for this change.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.25.1
    • addedInput schema / properties / card_id / description
      Added value: +"Id of the card to update, from card_builder_list_cards."
    • addedInput schema / properties / categories / description
      Added value: +"Replacement category list. Omit to leave categories unchanged."
    • addedInput schema / properties / config / description
      Added value: +"New DocumentData v3 block tree, replacing the whole config. Omit to keep the current config."
    • addedInput schema / properties / description / description
      Added value: +"New description text. Omit to leave it unchanged."
    • addedInput schema / properties / name / description
      Added value: +"New display name. Omit to leave the current name unchanged."
    • addedInput schema / properties / skip_version_bump / description
      Added value: +"If true, do not bump the card's stored version counter for this change."
    • addedInput schema / properties / tags / description
      Added value: +"Replacement tag list. Omit to leave tags unchanged."
  2. Addedv0.18.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=false; the description goes well beyond them by explaining the partial-update mechanics: omitted params are left untouched, but any supplied value (including config) fully replaces the prior value with no recovery. That 'no way to recover it afterwards' clause is exactly the irreversibility context an agent needs before a destructive write.

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?

Front-loaded with purpose, then behavioral contract, then Use-when / Not-for routing, then return value. Every sentence earns its place and there is no redundancy.

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?

For a 7-param destructive mutation with full schema coverage and an output schema present, the description closes the key gaps: replacement semantics, irreversibility, and the create-vs-update routing. Nothing an agent needs to invoke it safely is missing.

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?

Schema description coverage is 100%, so the baseline is 3, but the description adds genuinely new semantics beyond the per-field 'Omit to leave unchanged' notes: it clarifies the whole-object replacement behavior for config and the write mechanism (only non-omitted params are sent to the update command). That is value the schema does not convey.

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?

Opens with a specific verb+resource ('Update fields of an existing Card Builder card') and immediately distinguishes itself from the create sibling ('Not for: creating a new card — use card_builder_create_card'). An agent can route between card_builder_create_card and this tool without opening either 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?

Explicitly enumerates the valid scenarios ('renaming a card, editing its config, or retagging it') and names the exclusion plus the alternative tool. Nothing is left to inference; when-to-use and when-not-to-use are both spelled out.

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