Skip to main content
Glama

anytype_get_type

Retrieve a specific object type from Anytype by providing the space ID and type ID to access structured data within your workspace.

Instructions

Obtiene un tipo específico

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesID del espacio
type_idYesID del tipo

Implementation Reference

  • The main handler function for 'anytype_get_type' that extracts space_id and type_id from arguments, makes an API request to retrieve the type details, and returns the JSON-formatted response.
    export async function handleGetType(args: any) {
      const { space_id, type_id } = args;
      const response = await makeRequest(`/v1/spaces/${space_id}/types/${type_id}`);
      return { content: [{ type: 'text', text: JSON.stringify(response, null, 2) }] };
    }
  • The tool schema definition including name, description, and input schema requiring space_id and type_id.
    {
      name: 'anytype_get_type',
      description: 'Obtiene un tipo específico',
      inputSchema: {
        type: 'object',
        properties: {
          space_id: { type: 'string', description: 'ID del espacio' },
          type_id: { type: 'string', description: 'ID del tipo' },
        },
        required: ['space_id', 'type_id'],
      },
    },
  • src/index.ts:150-151 (registration)
    The switch case registration in the main tool dispatcher that routes 'anytype_get_type' calls to the handleGetType handler.
    case 'anytype_get_type':
      return await handleGetType(args);
  • src/index.ts:89-89 (registration)
    Inclusion of typeTools array (containing the schema) into the master tools list for tool discovery.
    ...typeTools,
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states it 'gets' a type, implying a read operation, but doesn't disclose behavioral traits such as error handling, permissions required, rate limits, or what happens if the type doesn't exist. This leaves significant gaps for safe invocation.

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 in Spanish ('Obtiene un tipo específico'), which is appropriately concise and front-loaded. However, it's under-specified rather than truly concise, as it lacks necessary detail for clarity.

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 no annotations, no output schema, and a vague description, this is incomplete for a tool with 2 required parameters. The description doesn't explain what a 'type' is, what data is returned, or how it differs from similar tools, making it inadequate for reliable agent use.

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 'type_id') documented in the schema. The description adds no additional meaning beyond the schema, such as explaining relationships between spaces and types or format examples. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 'Obtiene un tipo específico' (Gets a specific type) states a vague purpose with a verb+resource but lacks specificity about what 'type' means in this context. It doesn't distinguish from sibling tools like 'anytype_get_object' or 'anytype_get_property', leaving ambiguity about what resource is being retrieved.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'anytype_list_types' (for listing types) and 'anytype_get_object' (for retrieving objects), the description offers no context, prerequisites, or exclusions to help an agent choose appropriately.

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