Skip to main content
Glama

Cobrain

by space.cobrain
OverviewDiscussionsAdmin

create_unit

Create a unit at path from _templates/<type>/ (type is free; a missing template is seeded from a preset or the generic one; then shape it with the user): _about.md and _decisions.md, born already written — ask the user first if you do not know what it is and why it is being opened. On an existing folder it only adds missing files. Then fill the rest of _about.md with the user.

Input Schema

NameRequiredDescriptionDefault
pathYes
typeYes
aboutNoRequired. What or who this unit is and why it is in the brain, a few lines from what the user said: goes in the card's first section. Never invented.
fieldsNo
decisionNoRequired. The first decision for _decisions.md, one line, e.g. «Opened to follow the spring campaign (Ale)».
workspaceNoUsually OMIT: the path finds its brain. Pass it only when a reply asks (new or ambiguous branch), with the brain the user named (if unclear ASK): id, 'mine', or owner name/email. A brain where the branch does not exist is refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / decision / description
      Previous value: -"Required. The first decision for decisions.md, one line, e.g. «Opened to follow the spring campaign (Ale)»."New value: +"Required. The first decision for _decisions.md, one line, e.g. «Opened to follow the spring campaign (Ale)»."
  2. Changed2 schema fields changed
    • addedInput schema / properties / about
      Added value: +{
+  "description": "Required. What or who this unit is and why it is in the brain, a few lines from what the user said: goes in the card's first section. Never invented.",
+  "type": "string"
+}
    • addedInput schema / properties / decision
      Added value: +{
+  "description": "Required. The first decision for decisions.md, one line, e.g. «Opened to follow the spring campaign (Ale)».",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / workspace / description
      Previous value: -"Brain to act on: its id, «mio» (yours), or the owner's name/email as shown by search. Usually OMIT it: a path that already lives in one brain is found there, for reads and writes alike. Pass it only when the tool tells you to (a NEW branch, or one that exists in several brains) — with the brain the user named; when they were not explicit ASK THEM. A brain where the branch does not exist is refused even if you name it."New value: +"Usually OMIT: the path finds its brain. Pass it only when a reply asks (new or ambiguous branch), with the brain the user named (if unclear ASK): id, 'mine', or owner name/email. A brain where the branch does not exist is refused."
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true). The description adds real value beyond that: a missing template is seeded from a preset or generic one, files are 'born already written', and an existing folder only gains missing files (i.e. it will not overwrite). It stops short of describing the response or permission requirements.

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

Conciseness3/5

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

Front-loaded with the core action, which is good, but the sentence is a run-on tangled with nested parentheses and dashes that make the workflow harder to parse than it needs to be. It is information-dense rather than concisely structured.

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?

No output schema, so the description carries the return-value burden; it implies the created files but not the response shape. Given annotations cover the safety profile and the description covers the template-seeding and no-overwrite behavior, it is largely complete for a 6-param mutation tool, though param and response gaps remain.

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 coverage is only 50%: `path`, `type`, and `fields` have no schema descriptions. The description compensates for `type` by explaining it is free-form and how a missing template is handled, but says nothing about `path` format or the `fields` object, leaving real gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (create) and resource (unit) plus the mechanism (from `_templates/<type>/`), so an agent knows exactly what it does. However, it never references a sibling tool (e.g. list_units, write_file) to help disambiguate when this should be chosen over them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides procedural guidance ('ask the user first if you do not know what it is and why it is being opened') and a scoping condition ('On an existing folder it only adds missing files'), which is useful. But it gives no explicit when-to-use/when-not guidance relative to alternative tools like write_file or start_project.

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

All Cobrain toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources