Overview

RapidMCP lets you shape the response your tools return back to the model. You can provide a comma-separated list of field paths to extract, using one of three notations:

Notations

• Direct property name (top-level only)
• Dot notation (with optional array index: [n])
• JSON Pointer notation (slash-separated path starting with /)

When enabled, we build a flat object:

• The key is the direct property name (last segment).
• If multiple selected paths have the same last segment, we suffix the key with its parent path (underscored) to keep keys unique.

Example body

{
  "id": 123,
  "status": "ok",
  "profile": { "name": "Ada", "email": "ada@example.com" },
  "items": [
    { "sku": "A1", "qty": 2 },
    { "sku": "B2", "qty": 1 }
  ]
}

Direct property names

Notations:

id, profile

Result:

{
  "id": 123,
  "profile": { "name": "Ada", "email": "ada@example.com" }
}

Dot notation

Notations:

profile.name, items[1].sku

Result:

{
  "name": "Ada",
  "sku": "B2"
}

JSON Pointer notation

Notations:

/profile/email, /items/0/qty

Result:

{
  "email": "ada@example.com",
  "qty": 2
}

Duplicate keys

If multiple paths end with the same property name, the first one uses just the direct property name; subsequent ones receive a suffix based on their parent path.

Notations:

profile.name, /items/0/name

Result:

{
  "name": "Ada",
  "name_items_0": "A1"
}

Usage notes

• The list accepts spaces after commas (e.g., a, b, c).
• Invalid or non-existent paths are ignored.
• Enable the feature in the Tool’s Advanced section by toggling “Auto-formatted response properties,” then enter your paths.