Skip to main content
Glama

mitosis

by ai.mitosislabs

Connect link for one source

cortex_connect_link
Read-onlyIdempotent

The connect link for one memory source, by id — email and calendar (google-workspace), WhatsApp chats, GitHub, Notion, or file uploads. Returns the canonical mitosislabs.ai dashboard page where the user can connect that source to their memory, as a ready markdown link. Source ids appear in unconnected_sources on cortex_ask results and in cortex_connectable_sources; which source fits a question is the caller's judgment, made from each entry's answers and tags. link_text names, in the user's own words, what connecting answers — it becomes the connect page's title. Connecting itself is an authorization the user performs on that page; this tool only returns the link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
link_textNoLink text naming what connecting answers, in the user's words. Becomes the connect page title. Omit for a generic label.
source_idYesSource id exactly as listed, e.g. google-workspace, github, notion.

TDQS

A4.3/5.0
Behavior4/5

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

The description explicitly states that connecting is an authorization the user performs on the returned page and that this tool only returns the link, adding nuance beyond the readOnlyHint and idempotentHint annotations. It also clarifies how link_text is used, providing useful behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately sized but well-structured, leading with the core purpose and then providing supplemental context about source ids, link_text, and the tool's limited action. Every sentence contributes useful information without unnecessary repetition.

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?

Given the simple nature of the tool and the absence of an output schema, the description adequately explains the return value (a markdown link), the origin of parameters, and the boundary between this tool and the user's authorization step. It is complete enough for an agent to select and invoke it correctly.

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?

While the schema already documents both parameters at 100% coverage, the description adds meaning by explaining that source_id must be exactly as listed and appears in specific other tool outputs. It also elaborates that link_text becomes the connect page title, going beyond the schema's description.

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 clearly states the tool returns a ready markdown link for a memory source by id, listing supported source types. It distinguishes itself from sibling tools by emphasizing this is a link-returning tool, not the actual connection action.

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 description explains that source ids appear in unconnected_sources and cortex_connectable_sources, and that the caller judges which source fits from answers and tags. It clarifies that the tool only returns the link while the user performs authorization separately, providing clear context for when to use it.

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

All mitosis 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
Disambiguation2/5

There is significant overlap between cortex_ask, cortex_recall, and search, all of which retrieve from the user's memory. cortex_recall explicitly describes itself as a subset of cortex_ask, and search's description is nearly identical to cortex_ask's core function, making it hard for an agent to choose correctly. Other tools are more distinct, but this triple overlap creates real ambiguity.

Naming Consistency2/5

The naming is inconsistent: memory tools are split between a cortex_* prefix (ask, recall, manifest, status, etc.) and bare fetch/search, with no clear rule for which gets the prefix. Within cortex_*, some are verbs (ask, recall, remember) and some are nouns (manifest, status, connectable_sources), and platform tools use get_/list_/search_ prefixes, resulting in a mixed and unpredictable naming pattern.

Tool Count4/5

13 tools is a reasonable number for a server covering both memory operations and platform information. However, the presence of three overlapping retrieval tools (cortex_ask, cortex_recall, search) slightly inflates the count, suggesting some redundancy rather than each tool earning a unique place.

Completeness4/5

The server covers core workflows: reading memory (ask, search, recall, fetch, manifest), writing memory (remember, ingest_conversation), checking health (status), and accessing platform info (get_platform_status, get_pricing, list_skills, search_docs). Minor gaps include no explicit update/delete for individual memories and no direct tool to connect new sources (only listings of connectable ones), but these are often user-driven actions.

Resources