You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(messages): add forward_messages (batch) tool and strengthen guidance
Small models hosting the MCP client often pick the simpler branch of
`Union[int, List[int]]` and fall back to looping single-int forwards,
defeating the album-grouping preservation added in the previous commit.
Two changes to nudge them toward the correct path:
1. `forward_message`: rewrite the docstring as a directive ("USE A LIST
WHENEVER FORWARDING >1 MESSAGE") with an Args block FastMCP parses
for per-parameter descriptions. The model now sees the rule front and
center in the tool description, not buried in a paragraph.
2. New tool `forward_messages` (plural) with a pure `List[int]` signature
— no Union, no anyOf in the resulting JSON Schema. A list-only schema
is unambiguous: the model has no "int branch" to fall back on.
Backward-compatible: `forward_message` still accepts both `int` and
`List[int]`.
0 commit comments