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

starlink-enterprise-mcp

by WiFiWoW
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_addresses_by_address_reference_id

Read-only

Retrieves address information for a given address reference ID. Used to manage addresses in Starlink enterprise accounts.

Instructions

Get address — Required permission: Account information, View. — [GET /public/v2/addresses/{addressReferenceId}]

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>"
    },
    "name": "get_addresses_by_address_reference_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressReferenceIdYesAddress reference ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations provide readOnlyHint=true and destructiveHint=false, so the agent knows it is a safe read operation. The description adds permission requirement info but no further behavioral details (e.g., error handling, pagination).

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 extremely concise: three pieces of information (action, permission, endpoint) with no unnecessary words. It is well-structured and front-loaded.

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 simple read operation with one required parameter and no output schema, the description is mostly complete. It lacks explanation of return format, but the tool is straightforward enough.

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% (single parameter with description). The description does not add meaning beyond the schema; it does not explain what 'addressReferenceId' represents or how to obtain it.

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 states 'Get address' with a specific verb and resource. It is distinct from sibling 'get_addresses' which likely returns a list, and other CRUD tools like 'put_addresses_by_address_reference_id' and 'post_addresses'.

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?

The description mentions required permission but does not explicitly specify when to use this tool versus alternatives like 'get_addresses' (list) or 'put_addresses_by_address_reference_id' (update). Usage context is implied but not explicit.

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