Skip to main content
Glama

anytype_delete_type

Remove an object type from an Anytype workspace by specifying the space and type identifiers.

Instructions

Elimina un tipo de objeto

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesID del espacio
type_idYesID del tipo

Implementation Reference

  • The main handler function that executes the tool by making a DELETE request to the Anytype API endpoint for deleting a type.
    export async function handleDeleteType(args: any) {
      const { space_id, type_id } = args;
      const response = await makeRequest(`/v1/spaces/${space_id}/types/${type_id}`, {
        method: 'DELETE',
      });
      return { content: [{ type: 'text', text: JSON.stringify(response, null, 2) }] };
    }
  • Defines the tool schema including name, description, and input validation requiring space_id and type_id.
    {
      name: 'anytype_delete_type',
      description: 'Elimina un tipo de objeto',
      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:156-157 (registration)
    Registers the handler in the main tool dispatcher switch statement.
    case 'anytype_delete_type':
      return await handleDeleteType(args);
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. 'Elimina' implies a destructive mutation, but it doesn't specify permissions required, whether deletion is reversible, what happens to dependent objects, or error handling. For a deletion tool with zero annotation coverage, this is a significant gap in transparency.

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 sentence in Spanish that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with zero waste.

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's complexity as a deletion operation with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects like side effects, return values, or error conditions, which are crucial for safe tool invocation in a multi-tool environment.

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') clearly documented in the schema. The description adds no additional meaning beyond what the schema provides, such as explaining relationships between spaces and types. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Elimina un tipo de objeto' clearly states the action (eliminates/deletes) and the resource (object type) in Spanish. It's specific about what the tool does, though it doesn't explicitly differentiate from sibling tools like 'anytype_delete_object' or 'anytype_delete_tag', which lowers it from a perfect score.

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. With siblings like 'anytype_delete_object' and 'anytype_delete_tag', it's unclear what distinguishes deleting a type from deleting other entities. No prerequisites, exclusions, or context 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