Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

slack

Read-only

Read Slack — ops: usergroups, usergroup_members. Changes: slack_act.

  • usergroups: the workspace's user groups (@team handles) → {usergroups: [{id, name, handle, description, user_count, date_delete, prefs.channels, users?}]} — date_delete != 0 means disabled.

  • usergroup_members: usergroup → {usergroup, users: [U…]}, its member IDs.

Requires the usergroups:read scope, and a paid Slack plan.

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": {
      "op": "<op>"
    },
    "name": "slack"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYesWhat to read (see above).
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
_run_idNoOBLIGATOIRE à 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.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
usergroupNoUser group ID (S…) — `usergroup_members` only.
include_usersNo`usergroups` — add each group's member IDs.
include_disabledNoAlso return disabled groups (or read a disabled one).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=true, and the description goes well beyond that: it documents the return envelopes, explains that `date_delete != 0` means a group is disabled, and discloses the scope and paid-plan requirements. It omits pagination/rate-limit behavior, which keeps it from a 5.

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

Conciseness5/5

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

Front-loaded scope statement followed by two tight bullets, one per operation, each pairing the input with the exact response shape. There is no redundant or filler prose.

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?

For a 9-parameter read tool with no output schema, the description supplies the return shapes, the disabled-group semantics, and the access prerequisites, which is what an agent needs to call it correctly. Minor gaps remain around pagination and the infra parameters, but those are covered by the schema.

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 coverage is 100%, so the parameter descriptions already carry the load and baseline is 3. The description's bullets do add op-level meaning beyond the terse schema line "What to read (see above)", but it says nothing extra about the five oto infrastructure parameters or the filtering flags beyond what the schema states.

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 description names a specific verb ("Read Slack") and enumerates the exact two operations (`usergroups`, `usergroup_members`), plus what each returns. It also names the mutation sibling (`slack_act`) so the agent can distinguish read from write without opening the schema.

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?

It gives an explicit when-not ("Changes: `slack_act`") and states prerequisites (`usergroups:read` scope, paid Slack plan), which is real routing guidance. It does not, however, disambiguate against the other Slack read siblings such as `slack_list_channels` or `slack_read_history`, leaving the agent to infer from the op enum that this tool is usergroups-only.

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

All Tulina toolsInspect
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