Skip to main content
Glama

anytype_create_property

Add custom properties to objects in Anytype by defining key, name, type, and format to organize and structure data within your workspace.

Instructions

Crea una nueva propiedad

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesID del espacio
keyNoClave única de la propiedad
nameYesNombre de la propiedad
typeYesTipo de propiedad
descriptionNoDescripción
formatNoFormato específico
source_objectNoID del objeto fuente
read_only_valueNoSolo lectura

Implementation Reference

  • The handler function that implements the tool logic: validates inputs (space_id, name, type), constructs the request body, and makes a POST request to the Anytype API to create the property.
    export async function handleCreateProperty(args: any) {
      const { space_id, name, type, format, description, source_object, read_only_value = false, key, ...propertyData } = args;
      
      if (!space_id) {
        return { 
          content: [{ 
            type: 'text', 
            text: JSON.stringify({
              error: 'Missing required parameter',
              message: 'Field "space_id" is required for creating a property',
              provided_parameters: Object.keys(args)
            }, null, 2) 
          }] 
        };
      }
      
      // Validate required fields based on official API docs
      if (!name || !type) {
        return { 
          content: [{ 
            type: 'text', 
            text: JSON.stringify({
              error: 'Missing required fields',
              message: 'Both "name" and "type" are required for creating a property',
              required_fields: ['name', 'type'],
              provided_fields: Object.keys(args)
            }, null, 2) 
          }] 
        };
      }
      
      const requestBody = {
        name,
        type,
        format: format || type, // Format defaults to type if not provided
        description,
        source_object,
        read_only_value,
        key, // Optional unique key
        ...propertyData
      };
      
      const response = await makeRequest(`/v1/spaces/${space_id}/properties`, {
        method: 'POST',
        body: JSON.stringify(requestBody),
      });
      return { content: [{ type: 'text', text: JSON.stringify(response, null, 2) }] };
    }
  • Defines the input schema and metadata for the 'anytype_create_property' tool, specifying parameters, descriptions, and required fields.
    {
      name: 'anytype_create_property',
      description: 'Crea una nueva propiedad',
      inputSchema: {
        type: 'object',
        properties: {
          space_id: { type: 'string', description: 'ID del espacio' },
          key: { type: 'string', description: 'Clave única de la propiedad' },
          name: { type: 'string', description: 'Nombre de la propiedad' },
          type: { type: 'string', description: 'Tipo de propiedad' },
          description: { type: 'string', description: 'Descripción' },
          format: { type: 'string', description: 'Formato específico' },
          source_object: { type: 'string', description: 'ID del objeto fuente' },
          read_only_value: { type: 'boolean', description: 'Solo lectura' },
        },
        required: ['space_id', 'name', 'type'],
      },
    },
  • src/index.ts:140-141 (registration)
    Registers the tool in the main request handler switch statement, dispatching calls to the handleCreateProperty function.
    case 'anytype_create_property':
      return await handleCreateProperty(args);
  • src/index.ts:88-88 (registration)
    Includes the propertyTools array (containing the tool definition) in the combined list of all available tools for the MCP server.
    ...propertyTools,
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Crea una nueva propiedad' implies a write/mutation operation but provides no information about permissions required, whether the creation is reversible, rate limits, error conditions, or what happens on success/failure. This is inadequate for a mutation tool with zero annotation coverage.

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?

The description is extremely concise - a single Spanish phrase 'Crea una nueva propiedad'. While this is under-specified for the tool's complexity, it's not verbose or poorly structured. Every word contributes to the core meaning, though that meaning is insufficient.

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 (property creation) with no annotations, no output schema, and 8 parameters. The description is completely inadequate given the complexity - it doesn't explain what happens after creation, what the property affects, error conditions, or behavioral constraints. The agent would struggle to use this tool correctly based solely on the description.

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 8 parameters have descriptions in the schema. The tool description adds no additional parameter information beyond what's already documented in the input schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info 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 'Crea una nueva propiedad' (Creates a new property) is a tautology that essentially restates the tool name 'anytype_create_property'. It doesn't specify what kind of property (object property, space property, etc.) or what resource it operates on. While it distinguishes from deletion/update siblings by being a creation tool, it doesn't differentiate from other creation tools like 'anytype_create_object' or 'anytype_create_type'.

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's no mention of prerequisites, when this should be used instead of other property-related tools (like 'anytype_update_property' or 'anytype_get_property'), or what context requires property creation. The agent must infer usage from the name alone.

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