Skip to main content
Glama

anytype_update_space

Modify an existing Anytype workspace by updating its name, description, or icon to reflect changes in your organizational structure.

Instructions

Actualiza un espacio existente

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesID del espacio
nameNoNuevo nombre del espacio
descriptionNoNueva descripción del espacio
iconNoIcono

Implementation Reference

  • The main handler function that implements the tool logic: extracts space_id and update data, makes a PATCH request to the Anytype API endpoint `/v1/spaces/${space_id}`, and returns the formatted response.
    export async function handleUpdateSpace(args: any) {
      const { space_id, ...updateData } = args;
      const response = await makeRequest(`/v1/spaces/${space_id}`, {
        method: 'PATCH',
        body: JSON.stringify(updateData),
      });
      return { content: [{ type: 'text', text: JSON.stringify(response, null, 2) }] };
    }
  • Defines the tool metadata including name, description, and input schema specifying required space_id and optional fields like name, description, icon.
    {
      name: 'anytype_update_space',
      description: 'Actualiza un espacio existente',
      inputSchema: {
        type: 'object',
        properties: {
          space_id: { type: 'string', description: 'ID del espacio' },
          name: { type: 'string', description: 'Nuevo nombre del espacio' },
          description: { type: 'string', description: 'Nueva descripción del espacio' },
          icon: iconSchema,
        },
        required: ['space_id'],
      },
    },
  • src/index.ts:114-115 (registration)
    In the main switch statement, routes calls to 'anytype_update_space' to the handleUpdateSpace handler function.
    case 'anytype_update_space':
      return await handleUpdateSpace(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it's an update operation, implying mutation, but doesn't disclose permissions required, whether changes are reversible, rate limits, or what happens to unspecified fields. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 description is a single, efficient sentence ('Actualiza un espacio existente') that is front-loaded and wastes no words. It could be slightly more informative, but it's appropriately sized for a basic tool description.

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

Completeness2/5

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

Given the tool's complexity (4 parameters, nested objects, mutation operation) and lack of annotations and output schema, the description is incomplete. It doesn't explain return values, error conditions, or behavioral nuances. For an update tool with no structured safety or output info, more context is needed.

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%, with each parameter documented in the schema (e.g., 'space_id' as ID, 'name' as new name). The description adds no additional meaning beyond the schema, such as format details or constraints. With high schema coverage, the baseline is 3, as the schema does the heavy lifting.

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?

The description 'Actualiza un espacio existente' (Updates an existing space) states a clear verb ('actualiza') and resource ('espacio'), but it's vague about what specific aspects are updated. It doesn't differentiate from sibling tools like 'anytype_update_object' or 'anytype_update_type', which also update resources. The purpose is understandable but lacks specificity.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing space ID), exclusions, or compare to siblings like 'anytype_create_space' for creation or 'anytype_get_space' for retrieval. Usage is implied by the verb 'update', but explicit context is missing.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cryptonahue/mcp-anytype'

If you have feedback or need assistance with the MCP directory API, please join our Discord server