Skip to main content
Glama

Create or Replace Magic Dash Item

hudu_upsert_magic_dash_item
Idempotent

Create or replace a magic dash tile on a Hudu company page. Matches by title and company name; overwrites the existing tile or creates a new one to display current status.

Instructions

Create a magic dash tile, or replace the existing one with the same title on the same company. A magic dash item is one of the coloured tiles across the top of a company page in Hudu — a title, a headline message, an optional shade and optional HTML detail. They are normally written by scripts and integrations to surface a live status ("Microsoft 365: 42 licences, 3 unassigned") next to the documentation.

Read that first sentence carefully: this single endpoint does both. Hudu matches on title plus company_name, and if a tile with that pair already exists it is overwritten with what you send — no error, no warning, and no way to recover what it said before. Check hudu_list_magic_dash_items for the title on that company first whenever you are not deliberately refreshing a tile you own.

The replacement is wholesale rather than a merge: fields you omit are not carried over from the previous tile, so send the complete tile you want to end up with every time.

The write endpoints identify the company by name, not by id — company_id is a read-side filter only, and there is no way to address a tile by company id when writing. The name has to match an existing Hudu company exactly. Take it from company_name on a listed item, or from name on the record hudu_list_companies returns.

Operation class: Update. Impact: Overwrites any existing tile with the same title on the same company, wholesale and without confirmation. Creates a new tile only when no such pair exists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iconNoFont Awesome class shown in the tile header, e.g. "fas fa-circle".
shadeNoBackground colour of the tile, used to signal state at a glance — "success" and "danger" are the examples Hudu documents. Hudu publishes no closed list, so copy a value off an existing tile via hudu_list_magic_dash_items rather than inventing one.
titleYesHeading of the tile, e.g. "Microsoft 365" or "Backup Status". This is half of the match key: reusing a title that already exists on this company replaces that tile rather than adding a second one.
contentNoLonger detail revealed when the tile is opened, as HTML. Hudu renders this, so Markdown sent here is shown literally with its asterisks and pipes intact — use <table>, <ul>, <p> and <a href="..."> instead.
messageYesThe headline shown on the face of the tile — short, and usually the number or status the tile exists to report, e.g. "42 licences, 3 unassigned".
image_urlNoURL of an image to show in the tile header, as an alternative to an icon.
company_nameYesExact name of the company whose dashboard the tile belongs on. This is the other half of the match key. It must match an existing Hudu company name; there is no id form of this field.
content_linkNoURL the tile links out to, for sending a reader to the system the tile reports on.
Behavior1/5

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

The description transparently discloses overwrite behavior and irrecoverability, but it contradicts the annotation destructiveHint=false. The description says 'no way to recover what it said before' and 'Overwrites any existing tile... without confirmation,' while annotations mark the tool as non-destructive. Per rubric, contradiction yields a score of 1.

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 long but every paragraph earns its place: core purpose, non-obvious upsert/completeness behavior, company-name addressing, and impact statement. It is front-loaded and well-structured, avoiding fluff.

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?

For an 8-parameter mutation with no output schema, the description covers matching, overwrite semantics, wholesale replacement, and parameter nuances. The only notable gap is that it does not say what the call returns (e.g., the created/updated tile or just a status), which an agent may need since there is no output schema.

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

Parameters5/5

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

Schema coverage is 100%, and the description adds valuable context beyond schema: title and company_name form the match key, content must be HTML not Markdown, shade values are limited but not enumerated, and company_name is name-based not id-based. This significantly enriches parameter understanding.

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 'Create a magic dash tile, or replace the existing one with the same title on the same company,' a specific verb+resource+match condition. It clearly distinguishes this from list-only siblings by defining the upsert semantics and referencing hudu_list_magic_dash_items.

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 states when to check before using: 'Check hudu_list_magic_dash_items for the title on that company first whenever you are not deliberately refreshing a tile you own.' Also explains the alternative for list tools and how to obtain company_name from hudu_list_companies, giving clear usage guidance and exclusions.

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/ZenixSolutions/hudu-mcp'

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