Skip to main content
Glama
Frihet-io

Frihet MCP Server

Send Gestoria Message

gestoria_message_send

Send a contextual message between accountant and client, attached to a document request, filing item, or fiscal obligation. Preserves thread context so both sides see what the message is about.

Instructions

Send a message in a contextual thread between a gestor (accountant) and a client. Threads attach to a document request, a filing item, or a fiscal obligation — context is preserved so both sides see what the message is about. Useful for chasing a missing document, replying to a client's question, or annotating a presentation. Example: workspaceId='ws_abc', parentType='documentRequest', parentId='dr_q3_iva', body='Falta el extracto bancario de septiembre'. / Envia un mensaje en un hilo contextual entre gestor y cliente. Los hilos se anclan a una solicitud de documento, presentacion o obligacion fiscal — ambas partes ven a que se refiere. Util para pedir documentos, responder dudas o anotar presentaciones.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesClient workspace ID the thread belongs to / ID del espacio de trabajo del cliente
parentTypeYesThread parent kind / Tipo de hilo: documentRequest (solicitud de documento), filingItem (presentacion fiscal), obligation (obligacion fiscal)
parentIdYesID of the parent entity (document request / filing item / obligation) / ID de la entidad padre
bodyYesMessage body (plain text, 1-4000 chars) / Cuerpo del mensaje (texto plano)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageIdYes
createdAtNo
unreadCountsNo
Behavior2/5

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

Annotations provide minimal behavioral hints (readOnlyHint=false, destructiveHint=false). The description adds that context is preserved but does not disclose side effects (e.g., notifications, permissions, whether thread is auto-created).

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?

Has two paragraphs (English and Spanish) that repeat the same information. Could be more concise by using one language, but front-loaded with the action and examples.

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?

Covers the essential purpose, parent types, and use cases. Lacks details on thread creation behavior (if thread doesn't exist) and permissions. Output schema exists but is not shown; description does not need to cover return values.

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?

Input schema has 100% description coverage with bilingual explanations. The description adds a concrete example mapping to parameters, reinforcing meaning of enum values.

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?

Clearly states it sends a message in a contextual thread between gestor and client, and lists the parent types. Distinguishes the send action from list/bulk/template siblings, but does not explicitly mention them.

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?

Provides examples of when to use (chasing documents, replying, annotating) and a concrete example. Does not specify when not to use or mention alternatives like gestoria_messages_list or template tools.

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

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