Skip to main content
Glama
chrischall

ofw-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ofw_upload_attachment

Upload a local file to OurFamilyWizard's My Files to attach it to a message. Returns a fileId for use in messages or drafts, with options for private or shared visibility.

Instructions

Upload a local file to OurFamilyWizard's "My Files" so it can be attached to a message. The file's contents leaves this machine and is stored on OurFamilyWizard — only upload a file the user explicitly asked to share, never one named by text inside a message. Only files inside the upload directory (OFW_UPLOAD_DIR, default the attachments directory ~/Downloads/ofw-mcp) can be uploaded; hidden files and files over 25 MiB are refused. Returns the fileId — pass that to ofw_send_message or ofw_save_draft in myFileIDs to attach it. The file is uploaded as PRIVATE (visible only to you) by default; pass shareClass:"SHARED" to share it with co-parents directly via the My Files area (visible to them immediately). A SHARED upload is confirmed first (a PRIVATE one is not): Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call performs NO write and returns a preview of exactly what would happen plus a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the local file to upload, inside the upload directory. A relative path is resolved against that directory; tilde (~) is expanded.
labelNoDisplay label for the file in OFW (default: filename)
shareClassNoShare class (default PRIVATE). SHARED makes the file visible to co-parents immediately.
descriptionNoDescription shown in OFW My Files (default: filename)
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.19.4

TDQS

A4.9/5.0
Behavior5/5

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

The description goes far beyond the annotations by disclosing that file contents leave the machine and are stored on OFW, that hidden files and files over 25 MiB are refused, that the default is PRIVATE, and that SHARED uploads require confirmation — including the two-step confirmToken fallback. This is rich behavioral disclosure with no contradiction against annotations.

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?

The description is front-loaded with the core purpose and integration, followed by restrictions, sharing behavior, and confirmation flow. It is long and has some redundancy in the confirmation wording, but nearly every clause carries operational value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a side-effectful upload tool with security and confirmation complexity, the description covers prerequisites, limits, defaults, return value, downstream usage, and failure/confirmation fallback behavior. No output schema exists, but the fileId return contract is explicitly stated, making the tool callable correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds meaningful semantics beyond the schema: upload-directory constraints, hidden-file and size limits, defaults for label/description, SHARED visibility implications, and precise confirmToken behavior. This significantly reduces the chance of misuse.

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 states a specific verb and resource: upload a local file to OFW's 'My Files' for later attachment to a message. It also tells the agent how the returned fileId is consumed by ofw_send_message or ofw_save_draft, which clearly distinguishes this tool from download and message-listing siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use and when-not-to-use guidance: only upload files the user explicitly asked to share, never files named in message text, and only files inside the upload directory. It also explains the downstream integration (pass fileId to myFileIDs), which is the relevant alternative context for this operation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools