Tulina

Read-only

Reads WHATSAPP messaging via Unipile: 1-to-1 AND group conversations. Sending is whatsapp_act.

op:

"list" (default): the conversations, newest first, in items (limit 1-100). A cursor is returned only when Unipile paginates the channel (WhatsApp does not: a full page carries truncated). Group threads are listed alongside the 1-to-1 ones (is_group, named by the group's name) and read the same way. Each 1-to-1 thread is enriched with the counterpart's name (attendee_name); with_names=False turns this enrichment off (one API call fewer).
"read": the messages of a thread, 1-to-1 or group (chat_id from op="list"). A message Unipile passed on without text nor attachment carries content_unavailable. Each attachment carries a source: pass it to oto_import (target="project_file") to file it, or to any tool taking a source — the server fetches the file, never through the conversation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "whatsapp"
  }
}

Input Schema

Name	Required	Description	Default
`op`	No		list
`_org`	No	Org (id) de CET APPEL. `oto_list_orgs()`.
`limit`	No
`_group`	No	Équipe (id) de CET APPEL, sous son org parente.
`cursor`	No
`_run_id`	No	OBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
`chat_id`	No
`_account`	No	Compte à OPÉRER quand plusieurs existent. `oto_identity(op='list')`.
`_project`	No	Projet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
`_instance`	No	Instance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
`with_names`	No

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds real behavior beyond that: enrichment costs one extra API call when `with_names=True`, non-paginating channels return a `truncated` flag on a full page, relayed-without-content messages carry `content_unavailable`, and attachment `source` values are fetched server-side rather than through the conversation. It stops short of stating permission/account requirements, rate limits, or error behavior for `read` with a bad `chat_id`.

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?

Front-loaded with purpose and the sibling boundary before the per-op bullets, and every clause carries information (enrichment cost, group naming, attachment handling). The 'list' bullet is long and packs several unrelated facts into one paragraph, which slightly hurts scannability.

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

Completeness5/5

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

There is no output schema, and the description compensates by describing the return shape: `items`, `truncated`, `is_group`, group `name`, `attendee_name`, `content_unavailable`, and attachment `source`. For an 11-parameter, two-mode read tool, this is enough for an agent to call it and consume the result correctly.

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?

With 55% schema coverage, the description carries useful weight: it documents `op` modes and the default, the `limit` range (1-100), the meaning of `cursor`/`truncated`, `chat_id`'s provenance, and the cost trade-off of `with_names`. It says nothing about the six underscore-prefixed context parameters (`_org`, `_group`, `_run_id`, `_account`, `_project`, `_instance`), though those are documented in the schema itself.

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?

The first sentence names a specific verb and resource ('Reads WHATSAPP messaging via Unipile') and scopes it to 1-to-1 AND group conversations, while immediately excluding the write path ('Sending is `whatsapp_act`'). An agent can distinguish it from `whatsapp_act` and from the other messaging readers (`telegram`, `slack`) without reading any schema.

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

Usage Guidelines5/5

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

The description names the alternative for the outbound case (`whatsapp_act`) and then routes between its own two modes: 'list' for conversations, 'read' for messages of a thread with `chat_id` sourced explicitly 'from op="list"'. It also flags the case where a `cursor` is returned and states WhatsApp normally does not paginate, so the agent knows what to expect.

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

All Tulina tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?