Skip to main content
Glama

brainkb

by org.brainkb

brainkb_create_space

Create a workspace/space. The caller becomes owner. slug: lowercase/hyphen id, globally unique — if it's already taken the call returns 409 (pick another slug; slugs are never reused/deleted). visibility: 'private' or 'public'; description: short human description (recommended — surfaces in the registry); space_type: 'individual' (a personal space — any write-capable role) or 'team' (a shared space — only Admin/SuperAdmin, or a user granted create_team_space).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
slugYes
space_typeNoindividual
visibilityNoprivate
descriptionNo

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 fully carries the transparency burden: it discloses global slug uniqueness, 409 conflict behavior, slugs never being reused/deleted, visibility enum values, description surfacing in the registry, and owner designation. This is exceptional behavioral disclosure for a create operation.

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

Conciseness5/5

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

Compact and well-structured with labeled parameter descriptions. Every sentence carries information; purpose is front-loaded and there is no filler.

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?

Covers most operational aspects for a creation tool: ownership, uniqueness, role requirements, and parameter semantics. Missing the 'name' parameter and return value details, but the absence of an output schema makes return-value disclosure less critical.

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?

The description explains slug format/constraints, visibility allowed values, description purpose, and space_type semantics — all adding meaning beyond the bare string types in the schema. However, it omits the required 'name' parameter entirely, leaving its meaning to inference.

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 opens with 'Create a workspace/space' — a specific verb and resource — and immediately clarifies ownership ('caller becomes owner'), distinguishing it as the space-creation tool among many 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?

Provides clear role-based context for when to use space_type 'individual' versus 'team' (any write-capable role vs Admin/SuperAdmin or granted permission). It implies the tool's use for creation but does not explicitly name alternatives or when-not-to-use scenarios.

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

B3.4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, such as user management (activate, ban, assign role) vs. space management (create, add member, set visibility) vs. ingest/jobs (ingest_files, job_status, recover). A few pairs like grant_capability vs. grant_role_capability are similar but descriptions clarify the target, so an agent should be able to choose correctly.

Naming Consistency4/5

All tools are prefixed with brainkb_ and the large majority follow a verb_noun pattern (e.g., add_space_member, list_tokens, revoke_token). Some exceptions like brainkb_delta, brainkb_search, brainkb_whoami, and brainkb_capabilities break the pattern, but these are few and still readable.

Tool Count2/5

With 49 tools, the server is far above the 25+ threshold for 'too many'. While the broad scope (user admin, spaces, graphs, ingest, provenance, auth) justifies many operations, the sheer number makes it heavy and potentially unwieldy for an agent to navigate.

Completeness3/5

The tool set covers a wide range of use cases: user/role/capability management, space administration, graph registration, ingest, job monitoring, provenance, search, and SPARQL. However, there are notable gaps such as removing a space member, deleting a space, or updating space metadata, which could leave agents without a way to fully manage the lifecycle of a space.

Resources