Skip to main content
Glama

create_meeting

Crea una nueva reunión

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": {
      "name": "<name>",
      "date": "<date>",
      "meeting_type_id": "<meeting_type_id>"
    },
    "name": "create_meeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesFecha ISO (YYYY-MM-DD o timestamp)
nameYesNombre/título de la reunión
summaryNoResumen 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
transcriptionNoTranscripción
meeting_type_idYesID del tipo de reunión
meeting_group_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond the bare mutation verb: no note on duplicate creation risk (non-idempotent), what happens on missing required fields, or permission requirements.

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?

It is a single short sentence with no wasted words, but the brevity comes from under-specification rather than economy of expression; nothing substantive is front-loaded because nothing substantive is said.

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 7-parameter mutation tool with 3 required fields and no output schema, the description should at minimum convey creation semantics, required context (name/date/meeting_type_id), and the workspace_id omission rule. None of that appears, leaving the richer schema descriptions to carry the entire burden.

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 description coverage is 86%, so nearly every parameter is documented in-schema, giving the baseline of 3. The description contributes no additional parameter meaning, but it also does not need to under the rubric's high-coverage rule.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Crea una nueva reunión' merely restates the tool name (create_meeting) and title ('Crear una reunión') in Spanish, adding no scope, target resource detail, or differentiation from siblings like create_meeting_type or update_meeting.

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?

There is no guidance on when to use this versus alternatives such as update_meeting or create_event, no prerequisites, and no mention of required context like workspace scoping. The agent must infer everything from the schema.

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