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

saas-alerts-mcp

by am3cramirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

saas_alerts_devices_list_mapped

Read-onlyIdempotent

List devices mapped to customer organizations for SaaS Alerts by organization IDs.

Instructions

List devices that have been mapped (unified) to SaaS Alerts customer organizations.

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": {
      "organization_ids": "<organization_ids>"
    },
    "name": "saas_alerts_devices_list_mapped"
  }
}

Input Schema

NameRequiredDescriptionDefault
organization_idsYesOrganization IDs to filter by

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering safety. Description adds minimal extra behavior—only clarifying 'mapped' as 'unified'—and does not address pagination, output format, or required permissions.

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?

Single sentence, front-loaded with verb and object, no redundant words. Efficient and to the point.

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

Completeness3/5

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

Tool is simple with one required param and no output schema, but description does not mention what device fields are returned, pagination, or any operational nuances. It is adequate for a basic list but leaves some gaps.

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?

Schema description coverage is 100% with 'Organization IDs to filter by' for the only parameter. Description adds nothing beyond the schema, so baseline 3 applies.

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 uses specific verb 'List' and resource 'devices that have been mapped (unified) to SaaS Alerts customer organizations', clearly distinguishing it from sibling tools like devices_list_unmapped and devices_list_ignored.

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

Usage Guidelines3/5

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

The description implies usage for mapped devices but does not explicitly mention when to use this vs alternatives such as unmapped or ignored. It provides no exclusions or alternative tool references, relying on tool naming to differentiate.

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