Skip to main content
Glama

anytype_get_space

Retrieve a specific Anytype workspace by its unique ID to access and manage its content through the Anytype API.

Instructions

Obtiene un espacio específico por su ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesID del espacio

Implementation Reference

  • The main handler function that executes the tool logic: extracts space_id from arguments, makes API request to /v1/spaces/{space_id}, and returns the JSON response.
    export async function handleGetSpace(args: any) {
      const { space_id } = args;
      const response = await makeRequest(`/v1/spaces/${space_id}`);
      return { content: [{ type: 'text', text: JSON.stringify(response, null, 2) }] };
    }
  • The tool schema definition including name, description, and inputSchema requiring 'space_id'.
    {
      name: 'anytype_get_space',
      description: 'Obtiene un espacio específico por su ID',
      inputSchema: {
        type: 'object',
        properties: { 
          space_id: { type: 'string', description: 'ID del espacio' } 
        },
        required: ['space_id'],
      },
    },
  • src/index.ts:110-111 (registration)
    The switch case registration in the main CallToolRequestHandler that dispatches 'anytype_get_space' calls to the handleGetSpace function.
    case 'anytype_get_space':
      return await handleGetSpace(args);
Behavior2/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. While 'obtiene' implies a read operation, it doesn't specify whether this requires authentication, what happens if the space doesn't exist (error behavior), or what format the returned data takes. For a retrieval tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 a single, efficient Spanish sentence that communicates the core purpose without unnecessary words. It's appropriately sized for a simple retrieval operation and front-loads the essential information.

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

Completeness3/5

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

For a single-parameter retrieval tool with good schema coverage but no annotations and no output schema, the description is minimally adequate. It states what the tool does but lacks important context about authentication requirements, error handling, and return format that would help an agent use it correctly.

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?

The input schema has 100% description coverage, with the single parameter 'space_id' clearly documented as 'ID del espacio'. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline expectation when schema coverage is complete.

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

Purpose4/5

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

The description clearly states the action ('obtiene' - gets/retrieves) and the resource ('un espacio específico' - a specific space), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'anytype_get_object' or 'anytype_get_member' which suggests similar retrieval operations for different resource types.

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 like 'anytype_list_spaces' for browsing spaces or 'anytype_get_object' for retrieving other resources. There's no mention of prerequisites, context requirements, or typical use cases for retrieving a specific space by ID.

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