Skip to main content
Glama

anytype_update_property

Modify an existing property in Anytype by updating its name, description, format, source object, or read-only status within a specified space.

Instructions

Actualiza una propiedad existente

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesID del espacio
property_idYesID de la propiedad
nameNoNuevo nombre
descriptionNoNueva descripción
formatNoNuevo formato
source_objectNoNuevo objeto fuente
read_only_valueNoSolo lectura

Implementation Reference

  • The handler function that destructures arguments, validates required fields, builds the PATCH request body with provided updates, and calls the Anytype API to update the property.
    export async function handleUpdateProperty(args: any) {
      const { space_id, property_id, name, description, format, source_object, read_only_value, ...updateData } = args;
      
      if (!space_id || !property_id) {
        return { 
          content: [{ 
            type: 'text', 
            text: JSON.stringify({
              error: 'Missing required parameters',
              message: 'Fields "space_id" and "property_id" are required for updating a property',
              provided_parameters: Object.keys(args)
            }, null, 2) 
          }] 
        };
      }
      
      // Build update payload with only provided fields
      const requestBody: any = {};
      if (name !== undefined) requestBody.name = name;
      if (description !== undefined) requestBody.description = description;
      if (format !== undefined) requestBody.format = format;
      if (source_object !== undefined) requestBody.source_object = source_object;
      if (read_only_value !== undefined) requestBody.read_only_value = read_only_value;
      
      // Add any additional update data
      Object.assign(requestBody, updateData);
      
      const response = await makeRequest(`/v1/spaces/${space_id}/properties/${property_id}`, {
        method: 'PATCH',
        body: JSON.stringify(requestBody),
      });
      return { content: [{ type: 'text', text: JSON.stringify(response, null, 2) }] };
    }
  • The input schema definition for the tool, specifying parameters and required fields.
    {
      name: 'anytype_update_property',
      description: 'Actualiza una propiedad existente',
      inputSchema: {
        type: 'object',
        properties: {
          space_id: { type: 'string', description: 'ID del espacio' },
          property_id: { type: 'string', description: 'ID de la propiedad' },
          name: { type: 'string', description: 'Nuevo nombre' },
          description: { type: 'string', description: 'Nueva descripción' },
          format: { type: 'string', description: 'Nuevo formato' },
          source_object: { type: 'string', description: 'Nuevo objeto fuente' },
          read_only_value: { type: 'boolean', description: 'Solo lectura' },
        },
        required: ['space_id', 'property_id'],
      },
    },
  • src/index.ts:142-143 (registration)
    The switch case in the CallToolRequest handler that routes calls to this tool to the handleUpdateProperty function.
    case 'anytype_update_property':
      return await handleUpdateProperty(args);
  • src/index.ts:85-93 (registration)
    Inclusion of propertyTools (containing this tool's schema) in the list of tools returned by ListToolsRequest.
    const tools = [
      ...spaceTools,
      ...objectTools,
      ...propertyTools,
      ...typeTools,
      ...tagTools,
      ...templateTools,
      ...listTools,
    ];
  • src/index.ts:46-52 (registration)
    Import of the handleUpdateProperty handler function used in the tool dispatch.
    import {
      handleListProperties,
      handleGetProperty,
      handleCreateProperty,
      handleUpdateProperty,
      handleDeleteProperty
    } from './handlers/properties.js';
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Actualiza' implies a mutation/write operation, but the description doesn't disclose any behavioral traits: no information about permissions required, whether changes are reversible, rate limits, side effects, or what happens when properties are updated. For a mutation tool with zero annotation coverage, this is completely inadequate.

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

Conciseness2/5

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

While the description is brief (one Spanish phrase), this represents under-specification rather than true conciseness. The single sentence doesn't earn its place by providing meaningful guidance beyond the tool name. A truly concise description would still convey essential context about what kind of property is being updated and when to use this tool.

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

Completeness1/5

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

This is a mutation tool with 7 parameters, no annotations, and no output schema. The description provides minimal information - just a tautological restatement of the tool name. For a tool that modifies properties in what appears to be a complex system (Anytype), the description should explain what properties are, what aspects can be updated, and the implications of changes. The current description is completely inadequate for the tool's complexity.

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 all 7 parameters are documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

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

Purpose2/5

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

The description 'Actualiza una propiedad existente' (Updates an existing property) is a tautology that essentially restates the tool name 'anytype_update_property' in Spanish. It doesn't specify what kind of property (object property, space property, etc.) or what aspects are updated. While it distinguishes from creation/deletion tools by mentioning 'existing', it doesn't clearly differentiate from similar update tools like 'anytype_update_object' or 'anytype_update_space'.

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

Usage Guidelines1/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. There are multiple update tools in the sibling list (update_object, update_space, update_tag, update_type), but the description doesn't indicate this is specifically for updating properties rather than other entities. No context, prerequisites, or exclusions are mentioned.

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