Skip to main content
Glama
RestDB

Codehooks.io MCP Server

by RestDB

remove_schema

Remove the existing JSON schema validation from a collection, allowing any JSON document to be stored.

Instructions

Remove JSON schema from a collection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionYesCollection to remove schema from

Implementation Reference

  • Zod schema definition for remove_schema tool input validation. Defines a single required parameter 'collection' (string) describing which collection to remove the schema from.
    const removeSchemaSchema = z.object({
        collection: z.string().describe("Collection to remove schema from"),
    });
  • src/index.ts:365-376 (registration)
    Tool registration entry in the tools array. Defines the tool name 'remove_schema', description 'Remove JSON schema from a collection', and links to the removeSchemaSchema for input validation. Registered with required parameter 'collection'.
    {
        name: "remove_schema",
        description: "Remove JSON schema from a collection",
        schema: removeSchemaSchema,
        inputSchema: {
            type: "object",
            properties: {
                collection: { type: "string", description: "Collection to remove schema from" }
            },
            required: ["collection"]
        }
    },
  • Handler implementation for the 'remove_schema' tool case within the CallToolRequestSchema switch statement. Extracts the 'collection' argument, builds a CLI command using 'coho remove-schema' with project and space configuration, executes it via the executeCohoCommand helper, and returns the result as text content.
    case "remove_schema": {
        const { collection } = args as RemoveSchemaArgs;
        const removeSchemaArgs = [
            'remove-schema',
            '--project', config.projectId,
            '--space', config.space,
            collection
        ];
        const result = await executeCohoCommand(removeSchemaArgs);
        return {
            content: [
                {
                    type: "text",
                    text: result
                }
            ],
            isError: false
        };
    }
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states the action without discussing effects like whether the schema must exist, reversibility, or impact on data.

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?

A single sentence with no wasted words, achieving conciseness. However, it could be slightly more informative without becoming verbose.

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 simple one-parameter tool with no output schema, the description is adequate but lacks details on return values or side effects, leaving some completeness gaps.

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 coverage is 100%, so baseline is 3. The description adds 'JSON schema' context but repeats the schema's parameter description, providing marginal additional value.

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

Purpose5/5

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

The description 'Remove JSON schema from a collection' is clear with a specific verb (Remove), resource (JSON schema), and target (collection). It effectively distinguishes from sibling tools like add_schema and create_collection.

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, nor any prerequisites or conditions for removal. The description lacks context for optimal usage.

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/RestDB/codehooks-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server