Skip to main content
Glama

update_meeting

DestructiveIdempotent

Actualiza campos de una reunión existente

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": {
      "meeting_id": "<meeting_id>"
    },
    "name": "update_meeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
nameNo
summaryNo
meeting_idYesID de la reunión
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo
transcriptionNo
meeting_type_idNo
meeting_group_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is known. The description adds nothing on top: it does not say whether this is a partial or full-field replacement, whether omitted fields are cleared, or what permissions the caller needs for a destructive mutation.

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

Conciseness3/5

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

A single short sentence with zero padding, but the brevity comes from under-specification rather than discipline. There is nothing to front-load because nothing beyond the bare action is stated.

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?

A destructive 8-parameter mutation with no output schema and sparse parameter documentation needs far more than one line. The description leaves the agent without field semantics, partial-update behavior, or any confirmation of what the return looks like after a destructive edit.

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

Parameters1/5

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

With 8 parameters at only 25% schema coverage, the description carries a heavy burden and discharges none of it — it names no field at all (date, name, summary, transcription, meeting_type_id, meeting_group_id are all undocumented). An agent must guess what 'campos' means and whether meeting_type_id expects an ID or a name, mirroring the workspace_id ambiguity.

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 ('Actualiza') and resource ('campos de una reunión existente'), which cleanly separates it from create_meeting and get_meeting on scope alone. It stops short of naming any sibling explicitly, so it earns a solid 4 rather than a 5.

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

Usage Guidelines2/5

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

Beyond the word 'existente' implying this is not for creating new meetings, there is no guidance on when to reach for this versus update_meeting_type, confirm_meeting_actionable, or the other update_* siblings. No prerequisites, no mention of what happens if a field is omitted, no 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