Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

integration_status

Read-onlyIdempotent

Check your organization's setup status: plan, products, policies, licenses, API keys, service health and MCP calls, plus each product's setup progress and next steps.

Instructions

What's set up in the organization (plan, products, policies, licenses, API keys, license checks today, service health, today's MCP calls), each product's setup progress (parts done of total, the next part; every part's status for one product) and what to do next.

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

Input Schema

NameRequiredDescriptionDefault
productNoproduct id, code or name: every setup part's status for it; leave empty for each product's progress

Output Schema

NameRequiredDescriptionDefault
planYes
setupNoeach product's setup progress (the product's Setup tab)
usageYes
healthNo
limitsYesthe plan's limits; null means unlimited
apiKeysNoactive API keys
licensingNo
nextStepsYes
validationNo
organizationYes
mcpCallsTodayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds some useful scope by noting that license checks and MCP calls are 'today's' and that results include product setup progress, but it does not explain freshness guarantees, permissions, or how 'what to do next' is generated.

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

Conciseness3/5

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

It is a single sentence, but the nested parentheticals and semicolon-separated list make it dense and harder to parse. It front-loads the data domains but lacks a clear leading verb, and the product-specific clause is buried mid-sentence.

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 read-only, closed-world status tool with an output schema and full parameter coverage, the description covers the relevant data domains and the product parameter's effect. The main omission is guidance on when to use this aggregate view rather than individual list or analytics tools.

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 coverage is 100%, and the schema already explains that the optional product parameter accepts an id, code, or name and controls whether results are per-product progress or one product's part statuses. The description echoes the same semantics but adds no syntax, format, or edge-case detail beyond the schema.

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?

The description enumerates concrete domains it reports—plan, products, policies, licenses, API keys, license checks, service health, MCP calls—and per-product setup progress, so the resource is identifiable. However, it is a noun phrase without an explicit verb and does not explicitly distinguish itself from siblings like list_products or mcp_usage; the aggregation angle is implied rather than stated.

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

Usage Guidelines2/5

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

No explicit when-to-use guidance or alternatives are provided. The description implies an overview/setup status purpose through phrases like 'what to do next,' but an agent must infer when to choose this tool over the many list_* and analytics_* siblings.

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