MPFB MCP

Official

Overview Schema Source Related Servers Discussions Admin

mpfb_get_character_summary

Read-onlyIdempotent

Summarize a MakeHuman character before editing it: phenotype, rig, equipped assets, skin, targets, and face, in one read-only call. Use it first.

Instructions

Summarize one MakeHuman character before changing it, in one call: what it is, what it wears, and what its face is doing. Changes nothing. Call this first; call a detailed tool only for what the summary leaves out.

result carries one section per detailed tool: a subset of its fields under the same names, read by the same code, so the two never disagree.

phenotype - mpfb_get_macro_details.
rig - mpfb_get_object_info on the rig; null when there is none. rigify_role says whether it is a meta rig or generated.
equipped_assets - mpfb_get_object_info's related objects: every equipped garment, body part and body proxy, by type then name. Not capped.
skin - mpfb_get_object_info on the basemesh.
targets - mpfb_get_target_stack with its defaults: the modifiers rollup, asymmetries and the counts. Capped: if rollup_truncated, only the largest entries are here, and modifier_count/asymmetry_count give the whole.
face - mpfb_get_face_units (non-zero units only) and mpfb_get_expression (applied_expressions, matches_stack, unexplained_face_units). A non-empty unexplained_face_units is composed work the next mpfb_apply_expressions call destroys.

On a miss found is false and every section is null or empty.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say readOnly/idempotent/safe, but the description goes further: it explains the miss behavior ('found is false and every section is null or empty'), the truncation flag semantics ('rollup_truncated', 'modifier_count gives the whole'), and a genuine side-effect warning that a non-empty unexplained_face_units is work destroyed by a later call. That last point is behavioral context no annotation could carry.

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?

Front-loaded with the one-line purpose and a change-nothing guarantee, then a clean per-section breakdown. It's longer than most definitions but every bullet maps a section to its source tool and its caveats, so it earns the space. Minor redundancy across the 'read by the same code' framing.

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?

For a composite read tool with an output schema, it fully explains the section structure, provenance, truncation, and null/miss semantics, and even links the state to the next mutation tool. An agent knows exactly what it will receive and what a follow-up apply would risk.

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 0% and the only parameter (name, nullable with default null) is undocumented in the schema. The description never explains what name means or what a null/omitted name does, so it doesn't fully compensate. It's better than baseline only because the surrounding text implies single-character target selection.

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 ('Summarize one MakeHuman character') and scopes it to pre-modification reconnaissance with 'before changing it.' Clearly distinguishes itself from the detailed getters it delegates to by declaring the read-first role.

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?

Explicitly states when to use it ('Call this first') and routes to alternatives only when needed ('call a detailed tool only for what the summary leaves out'). Lists the exact detailed tools each section maps to, giving the agent an unambiguous triage path.

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