Skip to main content
Glama
jacob-hartmann

Quire MCP Server

quire.createDocument

Create a new document in a Quire organization or project, specifying name, markdown content, optional custom ID, dates, and icon.

Instructions

Create a new document in an organization or project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerTypeYesThe type of owner: 'organization', 'project', 'folder', or 'smart-folder'
ownerIdYesThe owner ID (e.g., 'my-org' or 'my-project') or OID
nameYesThe document name/title
idNoCustom ID for this document. If omitted, Quire generates one automatically. Must be unique within the project.
descriptionNoThe document content in markdown format
iconColorNoIcon color index from Quire's predefined palette
imageNoIcon image identifier (e.g., 'icon-view-list', 'icon-briefcase-o', etc.)
partnerNoOID of the external team this document belongs to
startNoTarget start date (ISO 8601 format, e.g., '2024-01-02')
dueNoTarget due date (ISO 8601 format, e.g., '2024-05-25')
Behavior2/5

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

No annotations exist; description only states 'Create' with no disclosure of side effects, permissions, idempotency, or return behavior.

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?

Extremely concise single sentence, but could be slightly expanded to include key context without losing brevity.

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 creation tool with 10 parameters and no output schema, the description is too sparse. Missing details on return value, error handling, and uniqueness of document names.

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% with clear parameter descriptions. Tool description adds no new meaning beyond the schema, so baseline 3 is appropriate.

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?

Description clearly states creation of a document in an organization or project, but misses the 'folder' and 'smart-folder' types from the schema, and does not differentiate from siblings like createTask.

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 on when to use this tool vs alternatives like createTask or createChat. No prerequisites or context provided.

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/jacob-hartmann/quire-mcp'

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