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

saas-alerts-mcp

by am3cramirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

saas_alerts_users_list_by_customer

Read-onlyIdempotent

Retrieve all users assigned to a specific SaaS Alerts customer by providing the customer ID.

Instructions

List all users belonging to a specific SaaS Alerts customer.

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": {
      "customer_id": "<customer_id>"
    },
    "name": "saas_alerts_users_list_by_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
customer_idYesCustomer ID to list users for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds no additional behavioral details such as pagination or return structure, but it aligns with the annotations.

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 description is a single, front-loaded sentence with no redundant words, making it highly efficient.

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

Completeness5/5

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

For a simple read-only, idempotent tool with a single parameter, the description and annotations provide sufficient context. It clearly communicates the action and scope, and the lack of an output schema is mitigated by the explicit 'List all users' phrasing.

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

Parameters3/5

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

The only parameter, customer_id, is fully described in the schema as 'Customer ID to list users for.' The description reinforces this by mentioning 'specific SaaS Alerts customer,' but adds no extra format or source information.

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 a specific action: 'List all users belonging to a specific SaaS Alerts customer.' It uses a precise verb and resource, with scope defined by 'specific customer,' distinguishing it from sibling tools like saas_alerts_users_list_partner.

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 establishes clear context: it is for listing users associated with a single customer. It does not explicitly mention alternative tools or exclusions, but the 'specific customer' scoping implies when to use it.

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