Skip to main content
Glama
berthelius

Frihet MCP Server

Bulk Send Gestoria Template

gestoria_template_bulk_send

Send a document request template to multiple client workspaces in a single call, respecting opt-out preferences and using period overrides to customize template variables.

Instructions

Send the same document request template to up to 500 client workspaces in one call. Each spawned request triggers the per-client notification handler (email + in-app). Honours allowGestoriaCommunications=false on the client user doc (opt-out). Uses periodOverrides to plug runtime values (quarter/year/month) into template variables. Returns a per-client outcome with success count, failures, and total wall-clock duration. Trust Area: RGPD — recipients must already have granted accountant access. Example: templateId='tpl_iva_q', clientWorkspaceIds=['ws_a','ws_b','ws_c'], periodOverrides={quarter:3, year:2026}. / Envia la misma plantilla a hasta 500 espacios cliente en una sola operacion. Respeta opt-out allowGestoriaCommunications=false.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templateIdYesTemplate ID (from `gestoria_template_create`) / ID de la plantilla
periodOverridesNoOverride template period variables in the bulk send / Sobrescribir variables de periodo (trimestre, ano, mes)
clientWorkspaceIdsYesTarget client workspace IDs (1-500) / IDs de espacios cliente destino

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
failedYes
successYes
totalDurationNoWall-clock duration in ms
Behavior4/5

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

Discloses notification handler trigger, opt-out respect, period variable plugging, and per-client outcome return. Annotations are minimal (not read-only, not destructive), so description carries burden and adds value with RGPD trust area mention.

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?

Efficiently structured with clear front-loading. Bilingual (English/Spanish) adds length but serves dual audience. Each sentence contributes useful information; no filler.

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

Completeness4/5

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

Covers main aspects: target, limits, opt-out, period overrides, notification, return type, and RGPD. Output schema exists so return value detail is not required. Adequate for its complexity.

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

Parameters4/5

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

Schema covers 100% of parameters with descriptions. Description adds context: periodOverrides used for runtime values, example provided, and max 500 limit for clientWorkspaceIds. Enhances understanding beyond schema.

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 it sends the same document request template to up to 500 client workspaces in one call. Distinguishes from siblings like gestoria_message_send (individual message) and gestoria_template_create (creation).

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?

Describes when to use (bulk sending) and mentions opt-out handling, period overrides, and notifications. Does not explicitly list alternatives or when-not-to-use, but sibling context provides implicit guidance.

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/berthelius/frihet-mcp'

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