Skip to main content
Glama

YouSpot

by com.youspot

Send Slack message

send_slack_message

Post a message to a Slack channel or DM as YouSpot, optionally as a reply in a thread. Only channels the bot has been invited to work; use list_slack_channels to find ids. Write in Slack markdown (bold, bullet lines, <url|label> links). Confirm with the user before posting anywhere others can see it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe message.
team_idNoThe workspace, when the user has more than one.
thread_tsNoReply in this thread instead of the channel.
channel_idYesWhere to post (C…/D… id).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint=false annotation, the description discloses the sending identity (YouSpot), Slack markdown expectations, the invitation restriction, and the requirement to get user confirmation before visible posting. This is meaningful behavioral context for a mutating, externally visible action.

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?

The description is front-loaded with the core purpose, then adds constraints in a logical order: channel eligibility, ID discovery, formatting, and user confirmation. Every sentence contributes practical information with no redundancy.

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 send operation, it covers the target, identity, allowed channels, message formatting, and confirmation requirement. It does not describe return values or error behavior, but these are not essential for correct invocation, and the missing details are minor for this tool.

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 coverage is 100%, so the baseline is 3. The description adds value by explaining that text should use Slack markdown and that channel_id can be discovered via list_slack_channels. thread_ts and team_id remain adequately covered by 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 description leads with a specific verb and resource: 'Post a message to a Slack channel or DM as YouSpot, optionally as a reply in a thread.' This clearly separates it from siblings like add_slack_reaction, get_slack_thread, and search_slack_messages.

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 actionable guidance: only channels the bot has been invited to work, use list_slack_channels to find ids, and confirm with the user before posting somewhere others can see it. It doesn't explicitly name alternatives, but no sibling tool duplicates this posting action, and the constraints make usage context clear.

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

All YouSpot toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools are scoped to a distinct resource and action, and descriptions do a good job separating close pairs like search_connections vs ask_about_connections or get_my_linkedin_posts vs linkedin_analytics. However, the multiple deletion tools (delete_graph_object, delete_graph_objects, purge_graph_object) and the several file-reading tools are easy to confuse without reading the descriptions carefully.

Naming Consistency4/5

The vast majority of tools follow a clear verb_noun pattern such as create_, get_, list_, search_, send_, and delete_. A handful of noun-phrase outliers like linkedin_analytics, mutual_connections, top_message_correspondents, and what_needs_attention break the pattern, so it is highly consistent but not perfect.

Tool Count1/5

64 tools is an extreme count, far beyond the typical well-scoped 3-15 tool range and even beyond the 25+ threshold for 'too many'. While the server covers many integrations, this many tools creates a heavy navigation burden and would be better split into focused servers per domain.

Completeness3/5

Core graph/CRM operations and read-side integration coverage are strong, with search, get, list, and create tools across most domains. However, there are notable dead ends: no delete_calendar_event, no tracker management beyond create_tracker, and set_follow_up explicitly lacks a read-back query tool, so some natural user requests cannot be completed through the toolset.

Resources