Skip to main content
Glama
Sign In
HullForge MCP Connector

HullForge MCP Connector

by jigwright
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Unreal API Lookup

hf_api_lookup
Read-onlyIdempotent

Search Unreal Engine API by plain-language query or class/function name for Blueprint-callable functions, signatures, asset factories, subsystems, settings, version-trap notes; no editor required.

Instructions

Search the Unreal Engine API on this machine: every Blueprint-callable function with its doc comment, class, signature and module, plus asset factories, subsystems, settings pages and HullForge's verified notes on engine version traps. Ask in plain words ("make a texture from a render target") or by name. Use it to understand the engine; to change the project, use hf_search_tools. Works without an editor open.

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": {
      "query": "<query>"
    },
    "name": "hf_api_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOptional. Only one kind of result.
limitNo
queryYesWhat you want to know or do, in plain words, or an engine class or function name.
editor_onlyNoOptional. Only functions from editor modules.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real context beyond them – that results are a local index of the engine with HullForge's curated notes on version traps, and that no editor session is required – but says nothing about result ordering, how limit interacts with broad queries, or what a miss looks like.

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?

Purpose and scope are front-loaded in the first sentence, followed by shorter sentences for input style, routing and availability – no filler. The opening sentence is long and dense, bundling payload contents, but each clause carries distinct information.

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 four-parameter read-only search with no output schema, the description covers what the results contain, how to phrase queries, and when to prefer a sibling. Only the shape of the response (per-result fields, ranking or truncation behaviour) is left implicit, which keeps it just short of complete.

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 75% and every parameter carries some description. The description still adds meaning by mapping the 'kind' enum values to concepts ('asset factories, subsystems, settings pages ... notes') and by clarifying that 'query' accepts either natural-language intent or an exact class/function name, including a worked example.

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?

States a specific verb and resource ('Search the Unreal Engine API on this machine') and then enumerates exactly what the index returns: Blueprint-callable functions with doc comment, class, signature and module, plus factories, subsystems, settings pages and verified version-trap notes. An agent can distinguish it from every sibling without opening the schema.

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?

Gives both input styles ('ask in plain words ... or by name') and an explicit use/do-not-use split: understand the engine here, change the project via hf_search_tools. The note that it works without an editor open is a concrete availability condition that shapes when an agent should call it.

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