Skip to main content
Glama

YouSpot

by com.youspot

Search Slack

search_slack_messages
Read-only

Search the Slack messages saved to the user's brain — by keyword and by meaning — newest first. Covers channels the user switched on and their DMs with YouSpot; nothing outside those. Optionally restrict to one channel (id or #name) or to messages since an ISO date. If it reports no Slack workspace connected, tell the user to connect one at /user/integrations/slack.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax messages (default 10, max 50).
queryYesWhat to look for.
sinceNoOnly messages sent on or after this ISO 8601 date.
channelNoA channel id (C…) or name ('#general') to search within.

Schema Changelog

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

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only provide readOnlyHint=true, so the description carries most of the behavioral burden. It adds meaningful context: the coverage limits, newest-first ordering, and what to do when no Slack workspace is connected. It doesn't fully explain the 'by meaning' mechanism or return shape, but it goes well beyond the annotation.

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 compact and efficiently structured: action with scope, optional filters, and error handling each get one clear sentence. Every sentence earns its place, and the most important capability is front-loaded.

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?

For a read-only search tool with fully documented parameters, the description covers the search scope, ordering, optional filtering, and the no-workspace edge case. The lack of an output schema is acceptable here because the tool's purpose and result ordering are clearly stated, making an agent's invocation safe and well-directed.

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%, and each parameter is already well described in the input schema. The description reinforces channel id/#name and ISO date formats, but it does not add significant semantic meaning beyond what the schema already provides.

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 opens with a specific verb and resource: 'Search the Slack messages saved to the user's brain,' and adds clear ordering behavior ('newest first'). It also defines scope precisely ('channels the user switched on and their DMs with YouSpot; nothing outside those'), which distinguishes it well from sibling search tools.

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?

The scope statement clearly tells the agent what is and is not covered, and the failure-handling instruction ('If it reports no Slack workspace connected...') gives concrete next-step guidance. It does not explicitly name sibling alternatives, but the boundaries are clear enough for an agent to decide when to use this tool.

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

A4/5.0
Disambiguation5/5

Each tool targets a distinct resource and action, with clear boundaries even within overlapping domains like LinkedIn (search vs. free-form query vs. profile vs. summary) and graph deletion (soft single, bulk soft, permanent single). Descriptions explicitly cross-reference related tools to prevent misselection.

Naming Consistency4/5

The vast majority follow a consistent verb_noun pattern (get_, list_, search_, create_, delete_, etc.). A few noun-phrase exceptions like linkedin_analytics, mutual_connections, similar_objects, and what_needs_attention deviate slightly, but they are still descriptive and do not create confusion.

Tool Count2/5

At 66 tools this is far beyond the 25+ threshold considered too many, even though the server covers many integration domains. Each domain has a coherent subset, but the overall surface is heavy for agents to navigate and would benefit from consolidation or namespacing.

Completeness4/5

The set provides deep read/search coverage across Gmail, Slack, Calendar, LinkedIn, HubSpot, Obsidian, Twitter, and a graph store, with core write operations for calendar, drafts, Slack, and graph objects. Minor gaps exist—notably no calendar delete, no direct Gmail send to third parties (only drafts), and no LinkedIn post/message actions—but these appear deliberate and do not block typical workflows.

Resources