Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

list_automations

Read-onlyIdempotent

Lists your organization's license-event automations with on/off status, problems, last run time, and monthly run usage against plan limits.

Instructions

List the organization's automations (trigger → conditions → actions rules that act on license events): on or off, problems, last run, runs this month against the plan.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
allowedYesthe plan includes automations
runsLimitYesthe plan's monthly runs; null = unlimited
automationsYes
runsThisMonthYeslive runs this month, across automations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world scope, so the safety profile is fully covered by structured data. The description adds that results are org-wide and summarizes the per-item status fields (on/off, problems, last run, runs this month vs plan), which is helpful selection context. It says nothing about pagination, ordering, or result volume, and the return-field detail overlaps with the existing output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the verb and resource, with the resource definition in parentheses rather than as trailing exposition. The final clause stacks several return attributes, which makes it slightly dense, but no sentence is wasted.

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?

With zero parameters, an output schema, and full annotation coverage, the definition only needs to say what is listed and at what scope, and it does both. The main residual gap is whether the listing is complete or paginated, which an agent might want before deciding to enumerate everything.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly does not invent parameter-like filtering options that the schema does not support.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List the organization's automations") and even defines the resource inline as trigger → conditions → actions rules acting on license events, which is far more than the name conveys. It does not explicitly distinguish itself from siblings like list_automation_runs or automation_catalog, but the resource is concrete enough to select on.

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?

Usage is only implied: an agent can infer this is the entry point for seeing what automations exist. There is no explicit when-to-use guidance, no mention of when to prefer list_automation_runs (run history) or automation_catalog (templates), and no exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.