Skip to main content
Glama

YouSpot

by com.youspot

Disconnect brain objects

disconnect_graph_objects

Delete one connection between two objects in the user's graph — the edge from_object_id -> to_object_id of the given connection_type, nothing else; both objects stay. Use get_graph_object to see an object's connections and their types and directions first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
to_object_idYesThe edge points here (exact object_id).
from_object_idYesThe edge starts here (exact object_id).
connection_typeYesThe relationship name of the edge to delete.

Schema Changelog

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

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses exactly what gets destroyed (only the single directed edge of the specified type) and what is preserved (both objects). This goes beyond the minimal readOnlyHint=false annotation and gives the agent a precise behavioral model.

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 sentences with no wasted words. The core behavior, scope, and exception are front-loaded in the first sentence, and the prerequisite is a useful second sentence.

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 simple deletion tool with fully documented parameters and a clear prerequisite, this is complete. It explains the action, the exact scope, the preservation of objects, and how to inspect connections before acting. No output schema is present, but none is necessary for such a focused mutation.

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%, so the schema already documents all three parameters. The description reinforces the from-to direction, but adds little semantic value beyond what the input schema 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?

States a specific verb ('Delete') and precisely defines the resource: one edge from from_object_id to to_object_id of the given connection_type. It also clarifies it deletes only the connection, not the objects, which distinguishes it from delete_graph_object and delete_graph_objects.

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?

Gives a clear prerequisite: use get_graph_object to inspect connections and their directions first. It also implicitly tells the agent when not to use this tool by emphasizing 'nothing else; both objects stay,' though it does not explicitly name alternative tools for deleting whole objects.

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