Skip to main content
Glama
Sign In
nomos-slack-mcp

nomos-slack-mcp

by project-nomos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

slack_list_users

List Slack workspace users, filtering by display or real name, to identify accounts for messaging or mentions. Set a result limit to keep responses focused.

Instructions

List users in a Slack workspace. Optionally filter by name.

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": "slack_list_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax users to return (default 50).
queryNoFilter users whose display name or real name contains this string.
workspaceNoWorkspace alias. Omit to use default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.5

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. The verb 'List' clearly signals a read-only operation and the optional filter adds useful behavior, but pagination behavior, default workspace selection, and any auth/rate concerns are not disclosed.

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?

Two short sentences with no fluff. The main verb and object are front-loaded, and the optional filtering behavior is stated economically. Every sentence earns its place.

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 simple list operation with no required parameters and a fully documented schema, this description is nearly sufficient. It lacks an explicit return-format or pagination note and does not mention that workspace defaults to the default workspace, but the schema covers the invocation parameters.

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 100%, with limit, query, and workspace all documented, including the default for limit and the matching rule for query. The description adds no meaning beyond the schema; 'filter by name' is actually less precise than the schema's display-name/real-name detail.

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 states a specific verb and resource: 'List users in a Slack workspace.' It also adds a distinct behavior, 'Optionally filter by name,' which clearly separates it from sibling listing tools such as slack_list_channels and slack_list_workspaces.

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?

The phrasing implies this tool is for retrieving Slack users, but it provides no explicit when-to-use guidance and does not reference alternatives. An agent must infer that this is the user-listing tool rather than channels/workspaces/search.

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

Deploy Server

Other Tools