mcptask.online

AddMessageTool

Add a note/message to a task with optional file attachment

Input Schema

Name	Required	Description
`content`	Yes	Message content (supports markdown)
`file_url`	No	Public https URL of the file to attach; the server downloads it
`file_name`	No	Filename with extension (required when using file_content, e.g., "screenshot.png")
`account_code`	Yes	Account code (e.g., "bcp", "jchsoft")
`file_content`	No	Base64-encoded file content (use this for remote MCP clients)
`signed_blob_id`	No	Signed blob id of a file already uploaded to a direct-upload URL
`task_relative_id`	Yes	Relative ID of the task to add message to

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / signed_blob_id

Added value: +{
+  "description": "Signed blob id of a file already uploaded to a direct-upload URL",
+  "type": [
+    "null",
+    "string"
+  ]
+}

Changed2 schema fields changedOct 14, 2026

removedInput schema / properties / file_path

Removed value: -{
-  "description": "Absolute path to file to attach (server-local files only)",
-  "type": [
-    "null",
-    "string"
-  ]
-}

addedInput schema / properties / file_url

Added value: +{
+  "description": "Public https URL of the file to attach; the server downloads it",
+  "type": [
+    "null",
+    "string"
+  ]
+}

First observedSep 14, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that attaching a file is optional, but says nothing about how the three mutually exclusive attachment paths behave (server-side download vs base64 vs pre-uploaded blob) — that context lives only in the schema property text.

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?

One sentence, front-loaded with the primary action, no filler. Appropriate for the amount of unique information it conveys.

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 7-parameter mutation tool with three interchangeable file-input modes and no output schema, the description omits the attachment-mode selection rule, whether an attachment can be combined with plain text, and what is returned. The schema patches parameter detail, but the overall behavior story is thin.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema carries the parameter detail; the description correctly flags that the attachment parameters are optional, which is the main semantic fact an agent needs at the top level. Baseline 3 plus a bit for calling out optionality of the 4 non-required attachment params.

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?

States a specific verb and resource: 'Add a note/message to a task', plus the attachment capability. An agent can identify the operation directly, though the overlap with sibling AddAttachmentTool is not addressed.

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 versus AddAttachmentTool, or when to use the three different file-supply mechanisms (file_url, file_content, signed_blob_id). The agent must infer usage entirely from the schema.

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

All mcptask.online tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?