Skip to main content
Glama
Sign In

busabase

by com.busabase
OverviewDiscussionsAdmin

Save the current space's global instructions (space managers only)

space_instructions_update

Save the current space's global instructions (space managers only)

PUT /api/v1/space-instructions

For multi-space accounts, call auth_verify, ask the user which space to use, and pass targetSpaceId. Space instructions are shared team background and default preferences: vision, mission, values, and design style. Read the latest version before each new task; the current user's explicit request takes precedence and this content never grants permissions or authorizes approving or merging change requests. Updating these settings requires workspace management access and the current expectedVersion. Change them only when the user asks; a conflict means reload and reconcile rather than overwrite.

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": {
      "body": "<body>",
      "expectedVersion": "<expectedVersion>"
    },
    "name": "space_instructions_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
targetSpaceIdNoBusabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.
expectedVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare it is a non-destructive write, and the description goes well beyond that: it requires workspace management access and expectedVersion, describes optimistic-concurrency conflict handling, warns that the content never grants permissions or authorizes merging change requests, and explains the precedence of the user's explicit request. That is substantive behavioral context an agent cannot get from the annotations.

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?

The title is echoed verbatim in the first line and the raw endpoint PUT /api/v1/space-instructions adds little for an agent, but the remaining sentences are dense with actionable constraints (auth, versioning, conflict handling, precedence) and reasonably front-loaded.

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?

For a mutation tool with no output schema, the description covers access requirements, concurrency, conflict recovery, and semantic limits of the stored content. The only gaps are the request body's concrete format and what the response returns, both minor for a save operation.

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 only 33%, so compensation is needed. The description explains expectedVersion's purpose ('current expectedVersion', reload-and-reconcile on conflict) and the multi-space flow for targetSpaceId, and clarifies what 'body' represents (vision, mission, values, design style) – though the body encoding/format is left implicit.

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+resource ('Save the current space's global instructions') and scopes it to space managers. It is clearly distinguished from the read counterpart space_instructions_get, which appears in the sibling list.

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

Usage Guidelines5/5

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

Explicitly says to change these settings only when the user asks, to read the latest version before each new task, and how to handle multi-space accounts (call auth_verify, ask the user, pass targetSpaceId). It also names the get sibling implicitly via 'read the latest version' and defines conflict behavior (reload and reconcile rather than overwrite).

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

All busabase toolsInspect
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.

Resources