Skip to main content
Glama
Sign In
saas-alerts-mcp

saas-alerts-mcp

by am3cramirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

saas_alerts_status

Read-onlyIdempotent

Check SaaS Alerts connectivity by fetching the authenticated MSP user and returning available domains with connection status.

Instructions

Check connectivity to SaaS Alerts by fetching the authenticated MSP user. Returns the list of available domains and connection status.

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": "saas_alerts_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint and idempotentHint, and the description complements this by explaining that it fetches the authenticated user and returns domains and connection status. This adds context about the operation's nature and output beyond the structured hints, with no contradictions.

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?

The entire description is two sentences with no redundant phrases. It front-loads the action ('Check connectivity') and immediately follows with the return value, making it easy to scan.

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?

For a parameterless status tool with no output schema, the description gives enough information: it states the outcome (connection status and available domains) and the mechanism (fetching the authenticated user). While it might not detail the exact structure of the status, the context is sufficient for an agent to invoke and interpret the result.

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?

There are no parameters in the schema, and the baseline for zero-parameter tools is 4. The description does not need to explain parameter semantics, and it doesn't try to invent any, so it adequately covers the input side.

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?

The description clearly states the tool checks connectivity to SaaS Alerts by fetching the authenticated MSP user, which is a specific verb-resource pair. It distinguishes itself from siblings like saas_alerts_users_get_msp by emphasizing connection status and domains rather than just user data.

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

Usage Guidelines4/5

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

The description provides a clear context for when to use this tool: to verify connectivity to SaaS Alerts. It does not explicitly name alternatives or exclusions, but the purpose is unambiguous enough that an agent can decide when a connectivity check is needed.

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