Skip to main content
Glama

quip_create_document

Create a new Quip document with a title and initial markdown content to start collaborative editing.

Instructions

Create a new Quip document

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the new document
contentYesInitial markdown content for the document

Implementation Reference

  • The handler function that executes the quip_create_document tool logic. It currently stubs out the implementation, noting that document creation is not yet supported in the Python script.
    private async createDocument(title: string, content: string) {
      try {
        console.log(`Creating document "${title}"...`);
        
        // Not implemented in the Python script yet
        return {
          content: [
            {
              type: 'text',
              text: `Document creation is not implemented in the current Python script. Please use the Quip web interface to create new documents.`,
            },
          ],
        };
      } catch (error) {
        console.error('Error creating document:', error);
        throw error;
      }
    }
  • src/index.ts:119-136 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining the tool's name, description, and input schema.
    {
      name: 'quip_create_document',
      description: 'Create a new Quip document',
      inputSchema: {
        type: 'object',
        properties: {
          title: {
            type: 'string',
            description: 'Title of the new document'
          },
          content: {
            type: 'string',
            description: 'Initial markdown content for the document'
          }
        },
        required: ['title', 'content'],
      },
    },
  • src/index.ts:180-186 (registration)
    Dispatch handler in the CallToolRequestSchema switch statement that validates arguments and invokes the createDocument handler.
    case 'quip_create_document': {
      const typedArgs = args as any;
      if (!typedArgs.title || !typedArgs.content) {
        throw new McpError(ErrorCode.InvalidParams, 'title and content are required');
      }
      return await this.createDocument(String(typedArgs.title), String(typedArgs.content));
    }
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 for behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't disclose important traits like permission requirements, whether the operation is idempotent, rate limits, or what happens on failure. It provides minimal behavioral context beyond the basic action.

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 that states exactly what the tool does with zero wasted words. It's appropriately sized for a simple creation tool and is front-loaded with the essential information.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns (e.g., document ID, success status), error conditions, or behavioral nuances. Given the complexity of document creation and lack of structured metadata, more context is needed.

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 (title and content) clearly documented in the schema. The description doesn't add any parameter semantics beyond what the schema already provides, so it meets the baseline of 3 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 clearly states the action ('Create') and resource ('new Quip document'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like quip_append_content or quip_prepend_content, which also modify documents but in different ways.

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. There's no mention of when this tool is appropriate (e.g., for creating entirely new documents) versus when to use sibling tools like quip_append_content (for adding to existing documents) or quip_read_document (for viewing).

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/AvinashBole/quip-mcp-server'

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