Skip to main content
Glama
jacob-hartmann

Quire MCP Server

quire.uploadTaskAttachment

Attach a file to a Quire task by supplying the task OID, filename, and content as a string. Optionally specify the MIME type.

Instructions

Upload a file attachment to a task. The content should be provided as a string (e.g., text content or base64-encoded binary).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskOidYesThe task OID (unique identifier) to attach the file to
filenameYesThe filename for the attachment (e.g., 'document.txt')
contentYesThe file content as a string
mimeTypeNoThe MIME type of the file (e.g., 'text/plain', 'application/pdf'). Defaults to 'application/octet-stream'
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 mentions content as string (text or base64) but lacks details on size limits, overwrite behavior, auth requirements, or error handling. Insufficient for understanding side effects.

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?

Two sentences, no filler. Purpose is front-loaded. However, it could be more structured with bullet points or additional details without sacrificing conciseness.

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 output schema, the description should explain return value (e.g., attachment ID) and error scenarios. It does not. Also missing limits (file size, MIME types) that would help the agent.

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 all parameters have descriptions. The description adds minor value by clarifying that content can be text or base64, but overall adds little beyond the schema.

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 verb (upload) and resource (file attachment to a task). It distinguishes from sibling 'uploadCommentAttachment' by specifying 'to a task'. However, it could be more specific about the types of content allowed (text or base64).

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 versus alternatives like 'uploadCommentAttachment' or other file-related tools. No mention of prerequisites, when not to use, or conditions for successful upload.

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