supervisor-api-client-function-calling

Execute client-defined function tools requested by the Supervisor API and resume conversations with outputs.

4|Updated May 9, 2026
One-click install
npx skills add https://github.com/victorlou/housing-assistant --skill supervisor-api-client-function-calling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supervisor-api-client-function-calling
Source: https://github.com/victorlou/housing-assistant/tree/main/app/app-templates/.claude/skills/supervisor-api-client-function-calling
Command: npx skills add https://github.com/victorlou/housing-assistant --skill supervisor-api-client-function-calling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of extending the Supervisor API with your own deterministic business logic by letting the model request client-executed functions and then continuing the conversation with their results.

Core Features & Use Cases

  • Client-side function tools: Register Python callables as type: "function" tools so your app executes them when the model returns a pending function_call.
  • Full turn continuation: Append prior response.output back into the next request input and include function_call_output items for every client call you executed.
  • Mixed hosted + client workflows: Combine hosted tools (including UC functions and MCP-approval flows) with client-side functions by filtering which function_call items your app must execute.

Quick Start

Use the supervisor client-side function calling flow to let an AI ask your application to compute a business rule, then return the result to the model for the final answer.

Frequently Asked Questions about supervisor-api-client-function-calling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute client-side functions alongside hosted tools in the Supervisor API?

To execute client-side functions alongside hosted tools, register Python callables as function tools and execute them when the Supervisor API returns a pending function call, then resume the conversation by appending the function call output.

Can I mix MCP tool calls and UC functions with my own custom business logic?

Yes, you can mix hosted tools like UC functions and MCP approval flows with custom business logic by filtering which pending function call items your application must execute locally.

What is the correct way to resume a conversation after executing a client-side function call?

To resume a conversation after a client-side function call, append prior response output back into the next request input and include function call output items matching the provided call ID.

Do I need to provide a JSON Schema for parameters when registering custom function tools?

Yes, registering custom function tools requires correct tool declarations with valid function name constraints and JSON Schema parameters to ensure the Supervisor API can request them properly.

Why does my client-side function tool execution fail to continue the conversation properly?

Client-side function tool execution fails if you do not echo the full response history per turn or append matching function call output items using the exact provided call ID.

When should I use client-side function calling instead of hosted tools for deterministic computations?

Use client-side function calling when your workflow needs custom business logic, external API calls, or deterministic computations that cannot be handled by hosted tools like UC functions.