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

tie-mcp-server

by taherkaraki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

test_syslog_by_syslog

Send a test syslog message to validate configuration and alert routing for specified input types.

Instructions

Send a test syslog 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_syslog_by_syslog"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesValidates the post /syslogs/test-message payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states 'send a test syslog notification' but does not explain that it actually transmits a syslog message to a specified server, or any side effects. The complex schema with IP, port, protocol, etc. suggests a network operation, but the description is too minimal.

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 under-specified. It does not earn its place by providing useful details beyond the name.

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?

Given the complexity of the input schema with conditional required fields and the lack of an output schema, the description should explain what a successful test does (e.g., sends a syslog message and returns a response). It only says 'send a test', leaving the agent without understanding of the actual operation or expected result.

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?

The single parameter 'body' has a schema description that is often just 'Validates the post /syslogs/test-message payload', which adds little meaning. The nested properties within 'body' (ip, port, protocol, etc.) have no individual descriptions. The description 'Send a test syslog notification' does not clarify what the parameters represent or how to use them.

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?

The description 'Send a test syslog notification' clearly states the action (send) and resource (test syslog notification). However, it does not differentiate from the sibling tool 'test_syslog', which could have a similar purpose.

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 like 'test_syslog' or 'test_email_notifier'. No prerequisites or context are provided.

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