get_platform_statusGet the operational status of the Mitosis website, API, and MCP server. Use before reporting an outage or debugging connectivity.
| Name | Required | Description | Default |
|---|---|---|---|
| service | No | Return only this service. Omit for all services. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and no destructive actions. The description adds context by specifying which services are checked, enhancing transparency without contradicting annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no wasted words. Action verb 'Get' front-loads the purpose, and the usage hint is immediately useful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one optional enum parameter and no output schema, the description covers purpose and usage adequately. Slight room for describing return format, but not necessary for this low-complexity tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and includes an enum with clear description. The tool description does not add extra parameter information, so baseline score applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves operational status of three specific services (Mitosis website, API, MCP server), distinguishing it from unrelated sibling tools like get_pricing, list_skills, and search_docs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly advises using this tool 'before reporting an outage or debugging connectivity,' providing clear when-to-use guidance. No exclusions or alternatives are given, but the context is strong.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.