Skip to main content
Glama

haus

by app.onehaus
OverviewDiscussionsAdmin

update_appliance

Update an appliance's details; omitted fields keep their current value. Rejects the update if the resulting warranty expiry date would fall before the purchase date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAppliance id from list_appliances.
nameNoNew name.
brandNoNew manufacturer or brand.
modelNoNew model.
notesNoFreeform notes.
purchaseDateNoPurchase date, YYYY-MM-DD. Must not follow warrantyExpiryDate. Empty string clears it.
serialNumberNoNew serial number.
warrantyDocumentIdNoWarranty document id from create_document.
warrantyExpiryDateNoWarranty expiry, YYYY-MM-DD. Must not precede purchaseDate. Empty string clears it.
insuranceDocumentIdNoInsurance document id from create_document.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
titleNo
messageNo
variantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / brand / description
      Previous value: -"New manufacturer or brand name. Omit to leave unchanged."New value: +"New manufacturer or brand."
    • changedInput schema / properties / id / description
      Previous value: -"ID of the appliance to update."New value: +"Appliance id from list_appliances."
    • changedInput schema / properties / insuranceDocumentId / description
      Previous value: -"ID of a previously created document containing the insurance policy. Omit to leave unchanged."New value: +"Insurance document id from create_document."
    • changedInput schema / properties / model / description
      Previous value: -"New model name or number. Omit to leave unchanged."New value: +"New model."
    • changedInput schema / properties / name / description
      Previous value: -"New name for the appliance. Omit to leave unchanged."New value: +"New name."
    • changedInput schema / properties / notes / description
      Previous value: -"Freeform notes about the appliance. Omit to leave unchanged."New value: +"Freeform notes."
    • changedInput schema / properties / purchaseDate / description
      Previous value: -"Date the appliance was purchased, in YYYY-MM-DD format. Omit or send null to leave unchanged, send an empty string to clear it. Must not be after warrantyExpiryDate."New value: +"Purchase date, YYYY-MM-DD. Must not follow warrantyExpiryDate. Empty string clears it."
    • changedInput schema / properties / serialNumber / description
      Previous value: -"New manufacturer serial number. Omit to leave unchanged."New value: +"New serial number."
    • changedInput schema / properties / warrantyDocumentId / description
      Previous value: -"ID of a previously created document containing the warranty paperwork. Omit to leave unchanged."New value: +"Warranty document id from create_document."
    • changedInput schema / properties / warrantyExpiryDate / description
      Previous value: -"Date the manufacturer warranty expires, in YYYY-MM-DD format. Omit or send null to leave unchanged, send an empty string to clear it. Must not be before purchaseDate."New value: +"Warranty expiry, YYYY-MM-DD. Must not precede purchaseDate. Empty string clears it."
  2. Changed21 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "01933f9c-7a2b-7c3d-8e4f-1a2b3c4d5e6f",
+    "notes": "Repaired ice maker under warranty, June 2026.",
+    "warrantyExpiryDate": "2026-11-04"
+  }
+]
    • addedInput schema / properties / brand / description
      Added value: +"New manufacturer or brand name. Omit to leave unchanged."
    • addedInput schema / properties / brand / examples
      Added value: +[
+  "Samsung"
+]
    • addedInput schema / properties / id / description
      Added value: +"ID of the appliance to update."
    • addedInput schema / properties / id / examples
      Added value: +[
+  "01933f9c-7a2b-7c3d-8e4f-1a2b3c4d5e6f"
+]
    • changedInput schema / properties / insuranceDocumentId / description
      Previous value: -"Document ID of insurance policy"New value: +"ID of a previously created document containing the insurance policy. Omit to leave unchanged."
    • addedInput schema / properties / insuranceDocumentId / examples
      Added value: +[
+  "doc_1a2b3c4d5e6f"
+]
    • addedInput schema / properties / model / description
      Added value: +"New model name or number. Omit to leave unchanged."
    • addedInput schema / properties / model / examples
      Added value: +[
+  "RF28R7351SG"
+]
    • addedInput schema / properties / name / description
      Added value: +"New name for the appliance. Omit to leave unchanged."
    • addedInput schema / properties / name / examples
      Added value: +[
+  "Kitchen Refrigerator"
+]
    • addedInput schema / properties / notes / description
      Added value: +"Freeform notes about the appliance. Omit to leave unchanged."
    • addedInput schema / properties / notes / examples
      Added value: +[
+  "Extended warranty purchased in-store, receipt in the kitchen drawer."
+]
    • changedInput schema / properties / purchaseDate / description
      Previous value: -"YYYY-MM-DD format"New value: +"Date the appliance was purchased, in YYYY-MM-DD format. Omit or send null to leave unchanged, send an empty string to clear it. Must not be after warrantyExpiryDate."
    • addedInput schema / properties / purchaseDate / examples
      Added value: +[
+  "2023-11-04"
+]
    • addedInput schema / properties / serialNumber / description
      Added value: +"New manufacturer serial number. Omit to leave unchanged."
    • addedInput schema / properties / serialNumber / examples
      Added value: +[
+  "S/N-4471829"
+]
    • changedInput schema / properties / warrantyDocumentId / description
      Previous value: -"Document ID of warranty"New value: +"ID of a previously created document containing the warranty paperwork. Omit to leave unchanged."
    • addedInput schema / properties / warrantyDocumentId / examples
      Added value: +[
+  "doc_8f3a1c2b9e4d"
+]
    • changedInput schema / properties / warrantyExpiryDate / description
      Previous value: -"YYYY-MM-DD format"New value: +"Date the manufacturer warranty expires, in YYYY-MM-DD format. Omit or send null to leave unchanged, send an empty string to clear it. Must not be before purchaseDate."
    • addedInput schema / properties / warrantyExpiryDate / examples
      Added value: +[
+  "2025-11-04"
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

The description adds meaningful behavioral detail beyond the annotations: omitted fields retain their current value, and the update is rejected if the resulting warranty expiry date precedes the purchase date. The annotations only indicate the tool is read-write and non-destructive, so this extra validation and merge behavior is valuable context.

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 concise sentences. The core action and update behavior are front-loaded, and the validation caveat follows without redundancy. Every word contributes useful information.

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 tool with ten parameters, a full output schema, and detailed property descriptions in the input schema, the description covers the essential behavioral context: partial updates and the warranty/date validation rule. Nothing critical for invoking the tool correctly 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. The description adds important parameter-level semantics not present in the schema: omitted fields are not reset and continue to hold their current value. It also clarifies the interaction between warrantyExpiryDate and purchaseDate, which directly impacts valid parameter combinations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Update an appliance's details.' It identifies the verb (update) and resource (appliance details) without ambiguity. It does not explicitly distinguish from sibling tools like create_appliance or delete_appliance, though the verb itself largely accomplishes that.

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 usage through the word 'Update' and the partial-update semantics ('omitted fields keep their current value'). It does not explicitly state when to prefer this over create or delete counterparts, nor does it mention exclusions. The partial-update guidance is useful but not full when-to-use guidance.

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

All haus toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources