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

starlink-enterprise-mcp

by WiFiWoW
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_data_pools

Read-only

Retrieve multi-service line enabled data pools filtered by product ID or pool IDs, with pagination support.

Instructions

Pre-Release: Get all multi-service line enabled data pools. — Required permission: Service plan, View.This endpoint is available for select audiences only. — [GET /public/v2/data-pools]

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_data_pools"
  }
}

Input Schema

NameRequiredDescriptionDefault
productReferenceIdNoFilter by Product ID of the pool
dataPoolIdsNoData pool IDs to filter by. Queries for all data pools on account if omitted
pageNoThe index of the page, starting at 0. Page size is 100. Default: 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds meaningful context about the tool being pre-release and restricted to select audiences, along with required permissions, exceeding what annotations provide.

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?

Description is concise (two sentences plus a path) with no wasted words. It front-loads the main action and includes critical access information efficiently.

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?

Description is adequate for a simple GET tool with full schema coverage, but lacks high-level context about the purpose of filters (productReferenceId, dataPoolIds) and pagination behavior beyond what's in the schema. No output schema, but not required for a list endpoint.

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?

Input schema has 100% description coverage for all 3 parameters. The description does not add any additional meaning beyond what the schema already provides, so baseline score of 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?

Description clearly states the verb 'Get' and the resource 'multi-service line enabled data pools'. It includes the HTTP method and path, distinguishing it from other get tools like get_data_pools_usage.

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?

Mentions 'Pre-Release' and 'available for select audiences only', indicating limitations, but provides no explicit guidance on when to use this tool versus alternatives or when not to use it.

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