Skip to main content
Glama

My UAV Forecast settings

get_my_settings
Read-onlyIdempotent

Answers: what are my limits and units, what does my plan include, which profiles and favorite locations do I have, and why did a verdict come out as it did. Favorite locations are listed by name only. Current factor keys: wind_at_altitude, max_altitude, temp_or_wind_chill, humidity, delta_t, precip_prob, precip_intensity, thunder_prob, cloud_cover, cloud_base, icing, visibility, sun_elevation, gps, kp, gps_kp, gust_at_altitude; unknown keys may appear.

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

Input Schema

NameRequiredDescriptionDefault
localeNoBCP 47 language tag for labels.

Output Schema

NameRequiredDescriptionDefault
linkNo
noteNo
unitsNo
sourceNoSource: UAV Forecast
statusYesok or subscription_required; others may appear.
accountNo
messageNo
profilesNo
thresholdsNo
unavailableNo
flying_hoursNo
plan_includesNo
saved_locationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real value: it discloses that favorite locations come back name-only (a lossy return the agent must not over-interpret) and that unknown factor keys may appear, warning against strict key handling. It does not mention auth/plan prerequisites, but the added return-shape caveats are substantive.

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?

The opening clause front-loads the four things the tool answers, and the follow-up sentences carry caveats. The 17-item factor-key enumeration is long but earns its place by letting the agent interpret verdict explanations; a couple of the clauses ('what are my limits and units') are slightly wordier than needed.

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?

An output schema exists, so return structure need not be spelled out, and the description still covers scope, the factor-key vocabulary, and two behavioral caveats. For a zero-required-parameter read tool this is close to complete; only the locale effect on output is left unspecified.

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?

There is a single optional parameter, locale, and the schema already documents it at 100% coverage as a BCP 47 language tag for labels. The description adds nothing about locale scope (e.g. whether it affects only labels or also values), so it sits at the baseline the schema earns on its own.

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

Purpose4/5

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

The description opens with an explicit enumeration of what is returned: limits and units, plan contents, profiles, favorite locations, and verdict explanations. That is specific enough to separate it from forecast/space-weather/places siblings, though it never states a verb like 'retrieve' and relies on the 'Answers:' framing to convey that this is a read of the caller's own account configuration.

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?

Usage is implied rather than stated: the 'why did a verdict come out as it did' phrasing hints this should be consulted when interpreting a verdict from a check tool, and the factor-key list supports that. There are no explicit when-not-to-use conditions and no named alternatives, so the agent must infer the workflow.

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