Skip to main content
Glama

anytype_get_property

Retrieve a specific property from Anytype objects by providing the space ID and property ID, enabling access to object data through the Anytype API.

Instructions

Obtiene una propiedad específica

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesID del espacio
property_idYesID de la propiedad

Implementation Reference

  • The handler function `handleGetProperty` that implements the core logic for the 'anytype_get_property' tool. It validates the required parameters (space_id and property_id), makes a GET request to the Anytype API endpoint `/v1/spaces/{space_id}/properties/{property_id}`, and returns the response as formatted text.
    export async function handleGetProperty(args: any) {
      const { space_id, property_id } = 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 getting a property',
              provided_parameters: Object.keys(args)
            }, null, 2) 
          }] 
        };
      }
      
      const response = await makeRequest(`/v1/spaces/${space_id}/properties/${property_id}`);
      return { content: [{ type: 'text', text: JSON.stringify(response, null, 2) }] };
    }
  • The schema definition for the 'anytype_get_property' tool, including input schema with required fields space_id and property_id.
    {
      name: 'anytype_get_property',
      description: 'Obtiene una propiedad específica',
      inputSchema: {
        type: 'object',
        properties: {
          space_id: { type: 'string', description: 'ID del espacio' },
          property_id: { type: 'string', description: 'ID de la propiedad' },
        },
        required: ['space_id', 'property_id'],
      },
    },
  • src/index.ts:138-139 (registration)
    Registration of the tool in the main MCP server request handler switch statement, which routes calls to the handleGetProperty function.
    case 'anytype_get_property':
      return await handleGetProperty(args);
  • src/index.ts:88-88 (registration)
    Inclusion of propertyTools (containing the schema) into the combined tools list served by the MCP server.
    ...propertyTools,
  • src/index.ts:46-52 (registration)
    Import of the handleGetProperty handler function from the properties handler module.
    import {
      handleListProperties,
      handleGetProperty,
      handleCreateProperty,
      handleUpdateProperty,
      handleDeleteProperty
    } from './handlers/properties.js';
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. The description only states it 'gets' a property, implying a read operation, but doesn't disclose any behavioral traits such as permissions required, error conditions, rate limits, or what happens if the property doesn't exist. For a tool with zero annotation coverage, this minimal description leaves significant gaps in understanding how it behaves.

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 extremely concise - a single Spanish phrase that directly states the action. While it's front-loaded and wastes no words, it's arguably too brief and under-specified rather than appropriately sized for the tool's complexity. However, it earns points for zero redundancy and clear structure within its limited scope.

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 has no annotations, no output schema, and operates in a complex system with many sibling tools, the description is inadequate. It doesn't explain what a 'property' means in this context, what format the returned property data takes, or how this tool fits within the broader Anytype ecosystem. For a read operation in a system with multiple retrieval tools, more context is needed for the agent to use it effectively.

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 both parameters ('space_id' and 'property_id') clearly documented in the schema. The description adds no additional meaning about these parameters beyond what the schema already provides. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description, which applies here.

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 'Obtiene una propiedad específica' (Gets a specific property) is a tautology that essentially restates the tool name 'anytype_get_property' in Spanish. It doesn't specify what kind of property (e.g., object property, space property) or provide any distinguishing context from sibling tools like 'anytype_get_object' or 'anytype_get_space'. The purpose is vague and 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 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. With sibling tools like 'anytype_get_object', 'anytype_get_space', and 'anytype_list_properties', there's no indication of when this specific property retrieval tool is appropriate or what distinguishes it from other get operations. No context 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