ToolRouter

Brain Admin

brain_admin

Brain admin operations. Pass action: "lint" | "link" | "promote" | "rebuild_index" | "team_sleep". team_sleep enables/disables/runs the nightly team consolidation cycle — pass sub_action "enable" (with optional timezone), "disable", "status", or "run_now". Team admin role required for team_sleep actions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "brain_admin"
  }
}

Input Schema

Name	Required	Description
`label`	No	Human-readable relationship label (for link).
`action`	Yes	Admin operation to perform.
`page_id`	No	Source brain page ID (for link/promote).
`team_id`	No	Team to promote to (for promote). Auto-resolved if on one team.
`timezone`	No	IANA timezone for team_sleep enable (e.g. "Europe/London"). Defaults to UTC. Sleep fires at 3 AM local time.
`sub_action`	No	Required for action="team_sleep". "enable" turns on nightly sleep for the team; "disable" turns it off; "status" shows last run and schedule; "run_now" triggers an immediate sleep cycle.
`to_page_id`	No	Target page ID (for link).
`relationship`	No	Relationship type (for link, e.g. relates_to, derived_from).

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already set readOnlyHint=false and destructiveHint=false, and the description usefully adds the team-admin authorization requirement plus the 3 AM local-time scheduling detail for team_sleep. However, it says nothing about the behavior or side effects of lint/link/promote/rebuild_index, which for a non-read-only, non-idempotent tool is a notable gap.

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?

Three tight sentences, front-loaded with the tool purpose and then the action set. It is efficient, with only mild redundancy from re-listing the action enum that already lives in the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-action tool with no output schema, only team_sleep is fleshed out; the other four actions have no behavioral or outcome context. The role requirement and timezone semantics are helpful, but the definition is incomplete for the majority of its operations.

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 description coverage is 100%, so the schema already documents every parameter including the sub_action enum and the IANA timezone default. The description mostly restates the sub_action values, adding little beyond what the schema fields already provide.

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

Purpose3/5

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

"Brain admin operations" is an umbrella phrase, and while the description enumerates the five actions (lint, link, promote, rebuild_index, team_sleep), it explains none of them beyond their names. An agent cannot tell what "promote" or "link" actually do, and it is unclear how the "lint" action differs from the sibling tool brain_lint.

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?

Guidance is given only for team_sleep (which sub_action to pass, and that the Team admin role is required). No when-to-use context is offered for lint, link, promote, or rebuild_index, nor any routing versus the closely related brain_lint sibling.

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

All ToolRouter tools Inspect

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.