Skip to main content
Glama
Sign In
tie-mcp-server

tie-mcp-server

by taherkaraki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

test_email_notifier_by_email_notifier

Send a test email notification to validate email notifier configuration for deviances, attacks, or health checks with customizable address and criticity threshold.

Instructions

Send a test email notification

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": {
      "body": "<body>"
    },
    "name": "test_email_notifier_by_email_notifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesValidates the post /email-notifiers/test-message payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'Send a test email notification' without mentioning any side effects, error conditions, permissions, or what 'test' implies. The agent cannot infer the behavior beyond a basic action.

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 a single short sentence, which is concise but not informative enough. It does not waste words but also does not add value beyond the tool name.

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

Completeness1/5

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

Given the complexity of the input schema (nested oneOf with conditional fields) and no output schema or annotations, the description is completely inadequate. It fails to explain what the tool does in terms of required inputs, test behavior, or expected results.

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?

Although schema description coverage is 100%, the tool description adds no meaning to the complex nested body parameter. The schema itself has a description but the tool description does not summarize or explain the conditional requirements based on inputType. Baseline is 3 but lack of compensation for complexity reduces score.

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

Purpose3/5

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

The description 'Send a test email notification' states the action and resource clearly, but it is very generic and does not differentiate from sibling tools like 'test_email_notifier' (also in the list). The name includes '_by_email_notifier' but the description does not clarify what that means, leaving ambiguity.

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 is provided on when to use this tool versus alternatives such as 'test_email_notifier' or 'test_syslog'. The description gives no hints about prerequisites, context, or exclusion criteria.

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