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

saas-alerts-mcp

by am3cramirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

saas_alerts_navigate

Read-onlyIdempotent

Browse a domain to see its available tools and descriptions. Discover the actions you can take for events, customers, users, devices, billing, reports, and partner data.

Instructions

Browse a domain to see its available tools and descriptions. All tools are callable at any time — navigation is optional discovery, not a gate.

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": {
      "domain": "<domain>"
    },
    "name": "saas_alerts_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to inspect. One of: events, customers, users, devices, billing, reports, partner

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering safety. The description adds valuable context that navigation is not a prerequisite for other tools, clarifying that it has no side effects and is purely informational. This exceeds the annotation baseline by explaining the tool's non-gating role.

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?

Two sentences with no filler. The first sentence states the action and object; the second clarifies the optional nature, both earning their place. Highly concise.

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 simple navigation tool with one enum parameter and strong annotation coverage, the description is sufficiently complete. It communicates the tool's purpose and usage context without missing critical behavior. The lack of output schema is acceptable given the tool's nature.

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 input schema fully documents the 'domain' parameter with an enum list and description, so schema coverage is 100%. The tool description adds no additional meaning to the parameter beyond what the schema provides. Baseline 3 is appropriate.

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's function: browsing a domain to discover available tools and descriptions. It distinguishes this from sibling tools, which perform actual operations, by positioning this as an optional navigation helper. The phrase 'navigation is optional discovery, not a gate' reinforces its unique role.

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 explicitly states that all tools are callable at any time and that navigation is optional, which tells the agent when this tool is not needed (before any operation). It provides clear context for using it as an exploratory aid without mandating it. It doesn't name alternatives, but the clarification 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