unreal-python-mcp

get_member_info

Retrieve detailed documentation for a specific class member, including its type, docstring, signature, and constant value.

Instructions

Get detailed documentation for a specific member of a class.

Returns the member type (method/property/constant), docstring, signature (for methods), and value (for constants).

Args: class_name: The class name (e.g., "Actor") member_name: The member name (e.g., "get_actor_location")

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": {
      "class_name": "<class_name>",
      "member_name": "<member_name>"
    },
    "name": "get_member_info"
  }
}

Input Schema

Name	Required	Description	Default
`class_name`	Yes
`member_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses return contents (member type, docstring, signature, value) beyond basic purpose, but does not mention error behavior or edge cases. This is strong for a read-only lookup.

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 appropriately compact, with a main goal sentence, a clear return summary, and an Args section with examples. Every sentence contributes useful information with no fluff.

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?

This is a simple two-parameter tool with an output schema. The description fully explains what it does and what it returns, so nothing critical is missing for proper invocation.

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 has 0% description coverage, so the description must compensate. The Args section provides clarifying examples (e.g., "Actor", "get_actor_location") for both parameters, adding meaningful semantics beyond the bare schema.

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 clearly states the tool retrieves detailed documentation for a specific class member, using a specific verb and resource. It distinguishes itself from the sibling get_members_info by emphasizing 'specific member'.

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 context is implied (for a specific member) but no explicit guidance contrasts it with alternatives like get_members_info or search_unreal_api. It lacks when-to-use or when-not-to-use guidance.

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

Deploy Server