moxie-mcp

attach_file_from_url

Download a file from a URL and attach it to a Moxie record. Supports clients, projects, deliverables, opportunities, expenses, and tickets.

Instructions

Attach a file to a Moxie record by providing a URL. The file will be downloaded and attached.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "id": "<id>",
      "fileUrl": "<fileUrl>"
    },
    "name": "attach_file_from_url"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The unique identifier of the object
`type`	Yes	Type of object to attach the file to
`fileUrl`	Yes	Valid HTTPS URL that Moxie will fetch the file from
`fileName`	No	Name to give the attached file

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jul 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Discloses that the file will be downloaded, but no details on side effects, permissions, size limits, or error handling. With no annotations, this is minimally adequate but not comprehensive.

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?

Two concise sentences, front-loaded with the action and resource. No superfluous information.

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

Completeness4/5

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

Sufficient for a simple file attachment tool with four parameters. Lacks mention of return value or error conditions, but the operation is straightforward.

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%, so the schema already provides clear parameter meanings. The description adds little beyond restating the URL method, warranting a baseline 3.

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?

Clearly states the verb 'attach', the resource 'file to a Moxie record', and the method 'by providing a URL'. Distinguishes from sibling tools, none of which perform file attachment.

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, or when not to use it. Lacks context about prerequisites or exclusions.

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