Skip to main content
Glama
Sign In
starlink-enterprise-mcp

starlink-enterprise-mcp

by WiFiWoW
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_routers_configs_tls

Read-only

Retrieves a paginated list of TLS configurations for routers on your Starlink account.

Instructions

Get TLS configs — Required permission: Device command and configuration, View.Gets a paginated list of TLS configs on this account. — [GET /public/v2/routers/configs/tls]

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

Input Schema

NameRequiredDescriptionDefault
pageNoIndex of page to get. Page size is 100. Default: 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already indicate read-only and non-destructive. Description adds permission requirement and pagination behavior, which is useful but not extensive.

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?

Two sentences effectively convey purpose and permission. The URL is extraneous but not harmful.

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?

Sufficient for a simple list tool with one parameter. Could hint at response structure but not required.

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 covers the single parameter 'page' with description. Description adds no extra semantics beyond schema.

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?

Clearly states the verb 'Get', resource 'TLS configs', and scope 'on this account'. Differentiates from siblings like 'get_routers_configs' and 'post_routers_configs_tls'.

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?

Mentions required permission, providing context on prerequisites. Does not explicitly exclude alternative tools but the name and description imply specificity.

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