Skip to main content
Glama

Search HubHop Presets

msfs_search_hubhop
Read-onlyIdempotent

Search the HubHop community preset database for MSFS aircraft control codes, covering more planes than built-in catalogs. Get executable RPN (like key events) to directly control your aircraft via SimConnect.

Instructions

Search the MobiFlight HubHop community preset database.

HubHop covers far more aircraft than the bundled catalogs, so this is the place to look when msfs_search_lvars finds nothing for the loaded aircraft. Each result's code field holds RPN -- typically (>K:...) or (>H:...) -- that you can pass directly to msfs_execute_calculator_code or msfs_trigger_custom_event, so a match here is immediately actionable, not just informational.

The first call in this server's session downloads the full preset database (roughly 32,000 presets, ~17 MB) and keeps it in memory; that call alone can take several seconds. This is expected, not a hang. Later calls, including to msfs_list_hubhop_aircraft, reuse the same in-memory copy and return quickly, for up to 6 hours -- after that the next call re-fetches automatically, since HubHop is a community database that keeps growing. Pass refresh=True to force an immediate re-fetch instead of waiting on that, e.g. right after publishing a new preset yourself.

Requires internet access. Supply at least one of query, vendor, aircraft or system -- the database is too large to browse unfiltered.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results
queryNoText to match against preset labels and RPN code, e.g. 'autopilot', 'landing light'
offsetNoResults to skip, for paging
systemNoSystem, e.g. 'Autopilot', 'Lights', 'Electrical'
vendorNoVendor name, e.g. 'FenixSim', 'PMDG', 'Asobo'
refreshNoBypass the cached preset database and re-fetch from HubHop before searching. Use this if you just added or changed a preset on HubHop and want to see it immediately, rather than waiting for the normal cache refresh.
aircraftNoAircraft model, e.g. 'A320', 'B737-800'
response_formatNo'markdown' for a table, 'json' for rowsmarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.1

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent/destructive annotations, the description discloses first-call latency from downloading ~32,000 presets, 6-hour memory caching, automatic re-fetch behavior, the need for internet access, and that returned RPN code is directly executable. This is exactly the kind of operational context annotations cannot convey.

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 long but tightly organized into purpose, differentiation, performance/cache behavior, and constraints. Every sentence provides actionable guidance—there is no filler, and the most decision-relevant facts are front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (8 optional params, no required fields, output format choice, external network dependency), the description covers all critical operational aspects: when to use it, what to expect on first call, how caching works, how to force refresh, and what to do with the results. Nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3. The description adds extra meaning by explaining the minimum filter requirement across query/vendor/aircraft/system, detailing when to use refresh=True ('right after publishing a new preset yourself'), and clarifying the semantic value of the code field in results.

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 opens with a specific verb and resource: 'Search the MobiFlight HubHop community preset database.' It also differentiates the tool from siblings by stating HubHop 'covers far more aircraft than the bundled catalogs' and framing it as the fallback when msfs_search_lvars finds nothing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is explicitly tied to a condition: 'this is the place to look when msfs_search_lvars finds nothing for the loaded aircraft.' It also gives a hard constraint, 'Supply at least one of query, vendor, aircraft or system,' and explains the cache/refresh behavior so the agent knows when refresh=True is appropriate.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/robin24/simconnect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server