Skip to main content
Glama

Starlink offer

starlink_offer
Read-onlyIdempotent

Current Starlink referral offer, Canada service-plans list prices, the time-limited homepage promo, the human Starlink page link, and disclosure. Read only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no repetition. The description does add something beyond them: that the homepage promo is time-limited (implying volatile results) and that a disclosure and human page link are bundled in. It still does not say whether results are live-fetched or cached.

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?

A single ~30-word sentence with no filler, though it is an unstructured comma list rather than a front-loaded statement of purpose. Nothing is wasted, but the leading item ('Current Starlink referral offer') is not clearly framed as the tool's function.

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?

With no output schema, the description carries the burden of describing return values, and it partly does by enumerating five content pieces. However, it leaves the response shape (structured object vs. formatted text block, and how the promo/disclosure fields are delimited) undefined for a zero-parameter tool whose entire value is its output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is an empty closed object, so there is nothing parameter-level for the description to clarify. Baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun-phrase list of contents (referral offer, Canada list prices, homepage promo, page link, disclosure) with no verb stating that the tool retrieves or returns them. The Starlink/Canada scoping does separate it from generic siblings like local_offer or content_offers, but the agent must infer the action.

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?

There is no statement of when to call this instead of local_offer, slipvault_offer, or content_offers, and no prerequisites or exclusions. The only usage-adjacent text, 'Read only,' is a restatement of an existing annotation rather than guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources