Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Edit a model

edit_model
DestructiveIdempotent

Update your own model's title, description, README, tags, license, or visibility after explicit confirmation, without uploading files and with no deletion options.

Instructions

Change details of the user's own model: title, description, README, tags, licence, visibility. Only after the user's explicit yes to the exact change. Doesn't use an upload. Nothing can be deleted with these tools.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model_id": "<model_id>"
    },
    "name": "edit_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoReplaces the tags.
titleNo
licenseNoSPDX id the user chose: MIT, Apache-2.0, GPL-3.0, BSD-3-Clause, CC-BY-4.0, CC-BY-SA-4.0, CC0-1.0.
model_idYesThe user's own model (id or page URL).
visibilityNoThe user's choice.
descriptionNo
readme_markdownNoThe whole new README (same sections as upload_model).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

The description contributes real behavioural context the annotations do not carry: a mandatory user confirmation step and the fact that no file upload is involved. However, "Nothing can be deleted with these tools" sits in tension with destructiveHint=true, since supplying tags "Replaces the tags" and readme_markdown replaces the whole README — an agent could read this as a safe additive edit. No partial-update semantics (what happens to fields left null) are given.

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?

Three short sentences, front-loaded with the resource and the field list, then the confirmation gate, then two clarifying negatives. No filler, though the closing "Nothing can be deleted" sentence is the one that adds ambiguity rather than clarity.

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 7-parameter mutation with annotations covering safety and idempotency, the definition covers the confirmation requirement and upload distinction but omits update semantics for unset fields and any note on what the result looks like. Adequate to invoke safely, not fully complete.

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 coverage is 71%, so several parameters are already documented (license SPDX ids, visibility choice, model_id, tags replacement, readme_markdown referencing upload_model sections). The description's field list matches the schema rather than extending it, and it does not explain the null default on six optional parameters — i.e. whether null means 'leave unchanged'.

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 names a specific verb (change) and resource (the user's own model) and enumerates the mutable fields: title, description, README, tags, licence, visibility. It also draws a boundary against the upload family with "Doesn't use an upload" and restricts scope to the user's own model, so the agent can separate it from upload_model/upload_version without opening their schemas.

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?

It states a hard precondition — only call after the user's explicit yes to the exact change — which is exactly the kind of gating an agent needs before a mutation. It does not, however, spell out alternatives (for example what to do when the model is not the user's own, or when a new README is better delivered via upload_version).

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