Skip to main content
Glama

update_model

Idempotent

Update the active model's metadata: name, documentation, and properties with merge support.

Instructions

Update the active model's name, documentation, and properties.

Updates is a dict containing only the fields to change; other fields
are left untouched and properties are merged into the existing ones.
There is no `model_id` parameter because exactly one model is active.
Works on a loaded model, not only on one created by this server.

Unlike `update_element`, unknown keys are rejected rather than
ignored: a mis-keyed update would silently leave model metadata
unwritten while still reporting success.

Args:
    updates: Mapping of fields to update. Supported keys:
        - `name` (str): New model name. Must be non-blank; it is
          stripped, exactly as in `create_empty_model`.
        - `description` (str): New model documentation. Reported
          back as `documentation`.
        - `documentation` (str): Accepted alias for `description`.
        - `properties` (dict[str, str]): Property updates merged
          into the existing model properties.

Returns:
    Success envelope with `data.model_info` (same shape as
    `pyarchimate://activemodel/info`).

Errors:
    `INVALID_MODEL_UPDATE` when `updates` is not an object or
        contains unsupported keys (`error.details.unsupported_keys`
        and `error.details.supported_keys` list which).
    `INVALID_MODEL_NAME` when `name` is present but not a non-blank
        string.
    `ModelNotFoundError` if no model is active.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
updatesYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Adds significant behavioral detail beyond annotations: updates are merged, properties are merged, unknown keys cause specific errors, idempotent behavior implied by merge semantics. Error cases are listed. No contradiction with annotations.

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?

Well-structured with Args, Returns, Errors sections and front-loaded purpose. Minor verbosity in error details could be streamlined, but every sentence adds value. Efficient for the complexity.

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?

Given the tool has one complex parameter and no output schema details shown, the description provides complete context: active model constraint, error types with details, return shape reference. No gaps for correct invocation.

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?

Input schema has 0% description coverage (just 'additionalProperties: true'), but the description's Args section fully defines supported keys, types, constraints (non-blank, stripped), aliases, and merge behavior. Compensates completely for schema lack.

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?

Clearly states 'Update the active model' with specific fields (name, documentation, properties). Distinguishes from sibling update_element by noting different behavior on unknown keys and clarifies it works on any loaded model, not just locally created ones.

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 contrasts with update_element ('unknown keys are rejected rather than ignored'), guides when to use each. Also explains the updates dict semantics (only change specified fields, merge properties) and the active model constraint, giving clear context for invocation.

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/byrondelgado/mcp-archimate'

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