Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

notify_set

Configure P5 mail notification settings; if unsupported, returns current settings, reason for no change, and GUI steps. Uses a password file path, not a password.

Instructions

P5 offers no API for its mail settings: returns the current settings, why nothing was changed and the GUI steps. Never takes a password as an argument (only a password file path).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "notify_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
tlsNo
portNo
userNo
senderNo
serverNo
confirmNoMust be true to actually run; without it only the plan/commands are returned
recipientsNo
passwordFileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

D1.9/5.0
Behavior2/5

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

With no annotations, the description must carry the behavioral burden; it does disclose the important limitation that there is no API and that a password is accepted only as a file path. However, it does not clarify whether any write occurs when confirm=true, what permissions are needed, or how the 'no change' result should be interpreted, and the schema's confirm wording ('actually run') sits uneasily with 'no API'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but it is front-loaded with a limitation and an awkward clause about return values, so the core purpose is not immediately clear. It is not padded, but the structure could be much better.

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 an 8-parameter, mutation-sounding tool with no annotations and no output schema, the definition is far from complete: most parameters are unexplained and the actual behavior is ambiguous. It does hint at returned diagnostic and GUI information, but not enough for an agent to invoke it confidently.

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

Parameters2/5

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

Schema coverage is 13% across 8 parameters, so the description needs to compensate; instead it mentions only passwordFile indirectly and leaves tls, port, user, sender, server, and recipients undocumented. The one useful addition beyond the schema is the prohibition on passing a raw password.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name implies configuring notifications, but the description opens with 'P5 offers no API for its mail settings' and then describes return content (current settings, why nothing changed, GUI steps) rather than a clear verb and resource. An agent cannot tell whether notify_set sets anything or only reports the limitation.

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

Usage Guidelines1/5

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

There is no when-to-use guidance and no comparison to notify_status or notify_test. The only constraint given concerns password handling, not when this tool should be selected.

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