Skip to main content
Glama

update_entity

DestructiveIdempotent

Actualiza campos de una entidad existente por ID

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": {
      "entity_id": "<entity_id>"
    },
    "name": "update_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasesNo
contextNo
entity_idYesID de la entidad
descriptionNo
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo
canonical_nameNoNuevo nombre canónico

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare the operation as non-read-only, destructive, idempotent, and open-world. The description adds only that the entity is existing and identified by ID, without explaining whether updates are partial or full, what happens to omitted fields, permissions needed, or destructive consequences.

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 with no unnecessary wording. It is efficient, though its brevity contributes to gaps captured in other dimensions.

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

Completeness2/5

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

For a destructive mutation with six parameters, half lacking schema descriptions, and no output schema, one sentence is not enough. The annotations cover safety traits, but the description should at least clarify partial-update behavior and the undocumented fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%, and the description adds no meaning beyond 'by ID' for entity_id. It does not clarify the undocumented aliases, context, or description parameters, nor how canonical_name or workspace_id interact with the update.

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 states a specific verb and resource: updating fields of an existing entity by ID. It is clear enough to distinguish from read/delete operations, though it does not differentiate from upsert_entity or other update_* siblings.

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 phrase 'entidad existente' implies the entity must already exist, which gives minimal when-to-use context. However, it does not explicitly compare with upsert_entity or other update alternatives, nor does it state prerequisites or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources