Skip to main content
Glama

YouSpot

by com.youspot

Check connections

list_integrations
Read-only

What the user has connected, and what they could connect. Returns every integration available to this account with connected true/false, the accounts behind it, the tools it unlocks, and the URL to connect or manage it. Call this BEFORE telling anyone to connect anything, and before saying a source is unavailable: guessing is how the assistant has told people to connect accounts they already had. An integration missing from the list is not offered to this user at all, so do not suggest it. suggested is what is worth connecting next, best first, each with the payoff in the user's terms: use it when asked what would help, and lead with the first one rather than listing the shelf. Connecting is a browser grant: hand the user the URL, never claim to have done it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoAsk about one integration only, e.g. 'linkedin', 'gmail', 'hubspot', 'slack', 'twitter', 'obsidian', 'sms'.

Schema Changelog

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

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description explains the semantic meaning of results: missing integrations are not offered, `suggested` is prioritized with user-terms payoff, and connecting is always a browser grant handed to the user, never performed by the assistant. This adds valuable disclosure that annotations alone do not convey.

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 dense but front-loaded with the core return contract, then layers usage rules, missing-integration semantics, suggested-field meaning, and connection behavior. Each sentence earns its place; no filler or repetition of the schema exists.

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?

With no output schema, the description carries the burden of explaining return values, and it does: connected flags, accounts, unlocked tools, URL, and the suggested field. It also covers the critical failure mode (guessing connectivity) and the user-facing connection flow, making it complete for correct invocation.

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 the single optional `key` parameter is already documented as 'Ask about one integration only.' The description does not add new parameter-level meaning beyond confirming the default all-integrations behavior, so it stays at the schema-covered baseline.

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 ('Returns every integration available') and resource, and details exactly what the output contains: connected status, accounts, tools unlocked, and manage/connect URL. This clearly distinguishes it from sibling tools like get_connection_details or search_connections, which are narrower in scope.

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?

It gives explicit call conditions: invoke before telling anyone to connect anything, and before claiming a source is unavailable. It also instructs when to use the `suggested` field and what not to do (do not suggest integrations missing from the list), providing concrete guidance an agent can act on.

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