Skip to main content
Glama

mitosis

by ai.mitosislabs
OverviewDiscussionsAdmin

Record what the user wants pulled out of a source

cortex_choose_enrichment
Idempotent

Record what the user wants Mitosis to pull out of a data source. A newly saved source WAITS: it is stored and searchable, but nothing is extracted from it until the user answers. When any save/ingest result carries choice.choice_required: true, ask the user its question and present EXACTLY two options: "Standard" (Mitosis extracts the people, companies, projects, topics, dates, and how they connect) or "Describe your goal" (the user says what they want extracted). Then call this tool with their answer. Never choose for the user and never infer an answer from silence. After cortex_list_goals, pass goal_ids to run those saved recipes on this source now. A brand-new goal is enough: Cortex writes the extract contract and starts extracting. Call it without choice to read the current state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNoA new goal, in the user's words. Required with describe_goal unless goal_ids is set.
choiceNo"standard", or "describe_goal" together with `goal` and/or `goal_ids`. Omit to read the current state.
feed_keyYesThe source, from `choice.feed_key` in the save/ingest result.
goal_idsNoSaved goals from cortex_list_goals to run on this source.
idempotency_keyNoOptional retry key; the same key never records twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / choice / description
      Previous value: -"\"standard\", or \"describe_goal\" together with `goal`. Omit to read the current state."New value: +"\"standard\", or \"describe_goal\" together with `goal` and/or `goal_ids`. Omit to read the current state."
    • changedInput schema / properties / goal / description
      Previous value: -"The user's goal, in their words. Required with describe_goal."New value: +"A new goal, in the user's words. Required with describe_goal unless goal_ids is set."
    • addedInput schema / properties / goal_ids
      Added value: +{
+  "description": "Saved goals from cortex_list_goals to run on this source.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=false and idempotentHint=true, and the description adds meaningful behavioral context: the source 'WAITS' until the user answers, extraction does not happen automatically, and the idempotency key behavior is implied via schema. The description also clarifies the two modes (standard/describe_goal) and the non-inference rule, which goes beyond the annotations.

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 long but every sentence carries necessary operational detail. It is front-loaded with the core purpose, then explains the trigger, options, and alternatives. While slightly dense, it avoids redundancy and is well-organized for an agent to parse.

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 tool's complexity (5 params, two modes, integration with cortex_list_goals), the description covers the main decision points: when to call, what to pass, and the read-only state. It does not describe the output format, but no output schema exists and the focus is on recording intent. The description adequately prepares an agent to use the tool 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?

Schema coverage is 100%, so the baseline is 3. The description adds context beyond the schema by explaining how parameters interact: `choice` determines mode, `goal`/`goal_ids` are used with describe_goal, and `feed_key` comes from the save/ingest result. This clarifies the conditional relationships that the schema alone does not convey.

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 states a specific verb ('record') and resource ('what the user wants Mitosis to pull out of a data source'), and clearly distinguishes its role from siblings like cortex_list_goals and cortex_ingest. The flow for when to call it is explicit, making its purpose unambiguous.

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?

Provides explicit when-to-use guidance: triggered by choice_required=true in save/ingest results, and instructs to present exactly two options. Also explains the alternative for running saved goals (cortex_list_goals) and the read-only mode when called without `choice`. It even states behavioral rules ('Never choose for the user'). This is comprehensive.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources