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

saas-alerts-mcp

by am3cramirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

saas_alerts_users_get_msp

Read-onlyIdempotent

Retrieve the MSP user profile linked to your API key to verify credentials and test connectivity.

Instructions

Get the MSP user profile associated with the authenticated API key. Also used as a connectivity / credential check.

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_users_get_msp"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the operation safe and idempotent. The description adds that the tool works as a credential check, which is a behavioral trait beyond the structured hints, and clarifies the association with the API key.

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?

One sentence, front-loaded with the main purpose, and efficiently adds a secondary use case with no redundant wording.

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 no-parameter, read-only tool with solid annotations, the description covers purpose, usage context, and return value, making it fully adequate.

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?

With zero parameters in the schema, the description explains that the operation uses the authenticated API key implicitly, providing meaning beyond the empty input schema. This fits the baseline for no-parameter tools.

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?

Description clearly states the tool returns the MSP user profile tied to the authenticated API key, with a specific verb and resource. This distinguishes it from sibling tools like partner_get_profile and 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?

Description identifies a key secondary use (connectivity/credential check) providing clear context for when to use. It does not explicitly mention alternatives or exclusions, but the context is sufficient.

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