Azquo

Edit name attributes

edit_name_attributes

DestructiveIdempotent

Surgical attribute edit on an existing name. Each entry in the attributes map sets that attribute on the named name; an empty string value deletes that attribute. Attributes not mentioned in the map are left untouched (this is NOT a wipe-and-replace).

Looks up by integer nameId — the id returned in apply_structure's namesResolved, or surfaced by describe_set / describe_query. Returns 404 if no name matches the id — silent no-op is never the result.

To rename a name, set its default_display_name attribute via this same call.

═══ PROVENANCE — required on every write ═══ source: where this edit originates — file path, URL, document name, or short note. Lands in the audit trail so the user can return to it. agent: your AI agent name (e.g. "Claude"). Lands in the audit trail so the user can see which AI made the edit.

Input Schema

Name	Required	Description
`agent`	Yes	AI agent name (e.g. "Claude"). REQUIRED.
`nameId`	Yes	Integer id of the name to edit (from apply_structure namesResolved, describe_set, describe_query, etc.)
`source`	Yes	Origin reference — file, URL, document, or short note. REQUIRED.
`business`	No	Optional. The business this call is for, by name, e.g. "azquo" - it then runs there whatever business the session is in. Worth giving on writes when you work in more than one business: a new MCP session starts in the login's own business. list_businesses shows the names.
`database`	Yes	Database name
`attributes`	Yes	Map of attribute-name → attribute-value (string). Empty value deletes the attribute. Values are stored verbatim, so JSON or other encoded content should be stringified by the caller and parsed on read.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026

addedInput schema / properties / business

Added value: +{
+  "description": "Optional. The business this call is for, by name, e.g. \"azquo\" - it then runs there whatever business the session is in. Worth giving on writes when you work in more than one business: a new MCP session starts in the login's own business. list_businesses shows the names.",
+  "type": "string"
+}

First observedOct 19, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=true): it discloses that empty values delete attributes, that unmentioned attributes are left untouched (explicitly NOT wipe-and-replace), that a missing nameId yields 404 rather than a silent no-op, and that source/agent are required provenance landing in the audit trail.

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 the core semantics in the first two lines, then lookup behavior, then a clearly headed PROVENANCE block. Sections are separated and each sentence carries distinct information despite the overall length.

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 destructive write with no output schema, the description covers the mutation semantics, failure mode (404), partial-update guarantee, provenance requirements, and the rename path. Nothing an agent needs in order to invoke it 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 coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains the delete-on-empty-string semantics of the attributes map, the verbatim storage rule, the source/agent audit purpose, and where nameId comes from — context the schema fields do not carry.

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?

States a specific verb and resource ('Surgical attribute edit on an existing name') and immediately distinguishes itself from a wipe-and-replace sibling behavior. It also names related tools (apply_structure, describe_set, describe_query) as sources of the nameId, so an agent can place it in the workflow.

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

Usage Guidelines4/5

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

Provides concrete when-to-use guidance, notably that renaming is done by setting default_display_name through this same call, and that the id comes from apply_structure/describe_* output. It does not, however, explicitly say when to prefer a different write tool (e.g. apply_structure or aql_write) over this one.

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

All Azquo 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?