PerfuMate

Edit a material

update_material

Use this when the user wants to change a material on their bench: their notes, odour description, families, note, impact, blotter hours, shelf life, synonyms, flash point, supplier IFRA limit or constituent breakdown; name and CAS only for their own materials.

Input Schema

Name	Required	Description
`cas`	No
`name`	No
`note`	No
`odor`	No
`tier`	No	The pyramid band it is filed in; null to derive it from its blotter hours.
`impact`	No
`natural`	No
`families`	No
`material`	Yes	The material: name, CAS or id.
`synonyms`	No
`flashPointC`	No
`blotterHours`	No
`constituents`	No
`dropsPerGram`	No
`personalNotes`	No
`shelfLifeMonths`	No
`supplierIfraLimit`	No	The supplier IFRA limit for this entry only; null removes it. It is not an IFRA Standard and never loosens one.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedInput schema / properties / supplierIfraLimit

Added value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "cat4Pct": {
+          "anyOf": [
+            {
+              "exclusiveMinimum": 0,
+              "maximum": 100,
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The Category 4 (fine fragrance) maximum from the supplier's IFRA certificate, as a % of the finished product; null if it states no restriction (recorded, never clears anything)."
+        },
+        "docRef": {
+          "description": "Issuer, title and document ID.",
+          "maxLength": 200,
+          "type": "string"
+        },
+        "issued": {
+          "description": "Certificate date, YYYY-MM-DD.",
+          "maxLength": 10,
+          "type": "string"
+        },
+        "note": {
+          "maxLength": 500,
+          "type": "string"
+        },
+        "supplier": {
+          "maxLength": 80,
+          "type": "string"
+        }
+      },
+      "required": [
+        "cat4Pct"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The supplier IFRA limit for this entry only; null removes it. It is not an IFRA Standard and never loosens one."
+}

First observedOct 18, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already disclose that this is a non-readonly, non-destructive, non-idempotent mutation, so the description need not restate safety. It adds a useful domain rule that name and CAS can only be changed for the user's own materials, but it does not explain partial-update behavior, validation failures, or how unspecified fields are treated despite idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence that starts with the trigger condition and then lists the editable fields. It is dense but every clause earns its place by naming an editable attribute; the only mild weakness is that the long field list makes it a run-on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 17-parameter mutation tool with 18% schema coverage and no output schema, the description gives a minimum-viable summary of what can be changed. It still leaves important gaps around update semantics (partial vs full replacement), how to identify the material, and what happens on invalid input, so an agent may need to infer behavior from the schema.

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 very low (18%), so the description must compensate. It maps most human-readable fields (notes, odour, families, impact, blotter hours, shelf life, synonyms, flash point, supplier IFRA limit, constituents) to parameters, but it omits notable parameters such as 'material', 'tier', 'natural', and 'dropsPerGram' and adds no units or format detail beyond the names.

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 uses a specific verb (change) and resource (material on their bench) and enumerates the editable fields, so the agent knows this is an edit operation rather than a read or create. It does not explicitly contrast with siblings such as update_formula or update_bottle, but the material focus is clear.

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 opening 'Use this when the user wants to change a material' gives a clear trigger condition and the closing 'name and CAS only for their own materials' adds a usage constraint. However, there is no explicit guidance on when not to use it or which sibling tool to choose for related operations.

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

All PerfuMate tools Inspect

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

Need Help?