Skip to main content
Glama
Sign In

brainkb

by org.brainkb
OverviewDiscussionsAdmin

brainkb_update_space

Rename a space, change its description, and/or give it a new slug. Owner/manager only. Pass only what changes; description="" clears it.

`new_slug` (lowercase letters, digits and hyphens, 3-64 chars) moves the space's IRI
and every graph whose IRI is built from the old slug (https://brainkb.org/graph/<slug>/…,
…/synthscholar/<slug>/…) to the new slug, with their registry, search and history
records and SynthScholar reviews; graphs with other IRIs keep theirs. The old slug and
IRIs stay as aliases: they keep resolving and nobody else can take them, but ingest
into an old IRI is refused with the new one. The result's `rename.moved_graphs` lists
each from → to. 409 if the slug or a target graph is taken.

Before calling with `new_slug`: show the user the graphs that will move and confirm.

Input Schema

NameRequiredDescriptionDefault
nameNo
slugYes
new_slugNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / new_slug
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "New Slug"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: it explains the IRI/graph migration, alias retention, that ingest into an old IRI is refused, the 409 conflict condition, and the rename.moved_graphs result field. This is exceptional behavioral disclosure for a mutation tool.

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?

Front-loaded with the action and permission gate, then the high-stakes new_slug semantics, then the confirmation requirement. The IRI-migration detail is long but warranted by the operation's complexity; no sentence is filler.

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?

No output schema exists, so the description helpfully names the returned field (rename.moved_graphs). Combined with permissions, conflict errors, alias behavior, and a safety confirmation step, an agent has everything needed to call this 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 0%, so the description must compensate. It adds real meaning for new_slug (charset and 3-64 char constraints, downstream IRI effects) and description (empty string clears it), plus the 'pass only what changes' rule. name is left unelaborated, but it is self-evident, so this is close to full compensation.

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 (rename/update) and resource (space) and enumerates the exact mutable fields: name, description, slug. An agent can immediately tell this apart from create_space, delete_space, and get_space among the siblings.

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 concrete when-to-use conditions: 'Owner/manager only', 'Pass only what changes', 'description="" clears it', and a required confirmation step before calling with new_slug. It lacks explicit alternatives (e.g. why not delete+recreate), so it falls just short of a 5.

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

All brainkb 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