starlink-enterprise-mcp

post_service_lines

Create a service line associated with an address and subscription product ID, optionally configuring data blocks.

Instructions

Create service line — Required permission: Service plan, Edit.Service line must be linked to an address and a subscription/product-ID, and can optionally be immediately configured with data blocks. — [POST /public/v2/service-lines]

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": {
      "addressReferenceId": "<addressReferenceId>",
      "productReferenceId": "<productReferenceId>"
    },
    "name": "post_service_lines"
  }
}

Input Schema

Name	Required	Description
`addressReferenceId`	Yes	Address Reference ID to associate with the service line. Example: 55ec6574-10d8-bd9c-1951-d4184f4ae467
`productReferenceId`	Yes	Subscription Product ID to associate with the service line. Example: business-subscription-100
`dataBlockProducts`	No	dataBlockProducts

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 13, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already indicate non-destructive write. The description adds that creation requires specific permissions and linkages, and optional data blocks. However, it does not disclose potential side effects like provisioning or billing impacts, which would be expected for a creation tool.

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?

The description is two concise sentences with the action front-loaded. It includes permission, constraints, and endpoint info without unnecessary exposition.

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?

Given the complexity of service line management and the lack of output schema, the description covers essential constraints but omits what the response contains (e.g., created service line ID). It is adequate but not fully complete for an agent to understand the return value.

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% with descriptions for each parameter. The description restates the required/optional nature of parameters but adds minimal new meaning beyond summarizing the schema in a sentence.

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?

The description clearly states 'Create service line' which is a specific verb+resource pair. It distinguishes itself from siblings by being the creation operation, while siblings are for retrieval, update, or deletion of service lines.

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?

The description provides usage context by specifying required permissions ('Service plan, Edit') and required linkages ('address and a subscription/product-ID'). It implicitly indicates this is for creating new service lines, but does not explicitly contrast with alternative tools like patch or post for sub-resources.

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

Deploy Server