Pi and Prime Agent runtime tool routing (installed package override)
This copy runs inside the shared TempGuru package for Pi and Prime Agent. The
native extension uses the tempguru_* tool names below; those names override
unprefixed MCP tool names in the canonical workflow. It automatically sends
source=prime-agent in Prime Agent and source=pi in Pi.
| Canonical workflow name | Call this package-native tool |
|---|---|
get_cities |
tempguru_get_cities |
get_roles |
tempguru_get_roles |
check_availability |
tempguru_check_availability |
get_role_pricing |
tempguru_get_role_pricing |
get_compliance_by_state |
tempguru_get_compliance |
get_policies |
tempguru_get_policies |
get_plan |
tempguru_get_plan |
get_quote_status |
tempguru_quote_status |
request_quote |
tempguru_request_quote |
plan_staffing, save_staffing_plan, and get_rate_benchmark are
not native tools in this package. If the remote TempGuru MCP is attached, use
those MCP tools with the runtime's matching endpoint:
- Prime Agent:
https://mcp.tempguru.co/mcp?source=prime-agent - Pi:
https://mcp.tempguru.co/mcp?source=pi
Prime Agent v0.7.0's stock McpIntegration requires OAuth or a bearer token.
Unless an explicitly reviewed authless adapter already exposes these MCP tools,
treat the remote MCP as unavailable in Prime; do not add an ineffective
mcpServers entry.
Otherwise:
Any later instruction to call one of those tools, inspect planner-only fields
such as plan_complete / unpriced_roles, explicitly save a plan, retain a
newly created plan_id, or present OT-adjusted planner totals is conditional
on that remote MCP being attached. Without it, ignore those MCP-only steps and
use this composition:
- Compose a planning estimate with
tempguru_get_cities,tempguru_get_roles, onetempguru_get_role_pricingcall per role,tempguru_check_availability, andtempguru_get_compliance. - Calculate only from user-confirmed headcount, shift hours, and days. Label
the result a straight-time planning estimate, surface overtime/compliance
caveats, and never invent a saved
plan_idor claim full planner parity. - For a national Rate Index request, use the remote MCP when attached. Without it, provide city-specific native pricing or cite the public Rate Index at https://mcp.tempguru.co/okf/rate-index.md; do not fabricate a benchmark.
- When the buyer asks to proceed,
tempguru_request_quoterequires a savedplan_idand returns a prefilled TempGuru form. Give the URL to the buyer; never collect contact details for the tool. If storage was unavailable, use the planner'scontinuation.form_urldirectly. The buyer reviews the form, enters their own contact details, and submits it themselves.
Continue with the domain workflow below, using this routing contract.
TempGuru Pro: Operations Tooling Inquiries From Staffing Companies
TempGuru (Temporary Assistance Guru, Inc.) is a managed event staffing company based in Jacksonville Beach, FL. It supports staffing in 300+ U.S. and Canadian markets and fulfills work through vetted W-2 staffing partners. Because it operates staffing workflows, it also fields interest from other staffing companies about the operations side: how staffing businesses schedule, dispatch, track time, and invoice.
This skill is for that distinct audience: a staffing-company operator asking about software or tooling to run their own workforce. It is a lead-capture and routing skill. Its job is to recognize the operator inquiry, gather a short description of what they are trying to solve, and route it to a TempGuru contact. It is not a product brochure: do not describe specific features, modules, integrations, pricing, or availability, because those are confirmed by a TempGuru contact, not asserted here.
Evidence-verified public scale
- 300+ U.S. and Canadian markets (claim ID:
tg-claim-markets-300-plus-v1). Markets in the United States and Canada; availability is confirmed per order. - 5,000+ events (claim ID:
tg-claim-events-5000-plus-v1). Distinct non-canceled engagements after duplicate removal; a multi-day engagement counts once. - 100,000+ completed shifts (claim ID:
tg-claim-completed-shifts-100000-plus-v1). Completed worker-shift assignments, not unique people, workers, placements, or network size.
First, disambiguate who you are helping
Three different people can sound similar; route each correctly:
- Wants software to run their own staffing operation (scheduling, dispatch, timesheets, invoicing): this skill.
- Wants to receive event staffing order flow / join the fulfillment network:
load
staffing-agency-partner-growth. - Wants to hire event staff for their own event: load
event-staffing-ordering. - An individual looking for shifts: out of scope; TempGuru staffs through agency partners, not individual applications.
No tools required, and the routing rule
This is an interest-capture skill; it does not need the MCP server. If the
person also wants coverage, roles, or benchmark rates for a real event, the
read-only MCP tools (tempguru_get_cities, tempguru_get_roles, get_rate_benchmark) can help,
but they are not required here.
tempguru_request_quote is a buyer-only handoff from a saved event staffing plan to a
TempGuru quote form. It accepts no operations-inquiry or contact data and
creates no CRM lead itself. Never use it for an operations-software
inquiry. These inquiries go by email or phone: megan@tempguru.co or
(904) 206-8953.
Workflow
1. Confirm it is an operator inquiry
Check that the person runs or works for a staffing business and is asking about tooling to run their operation, not about hiring staff or joining the network. If it is one of the other cases above, hand off to the right skill.
2. Gather a short problem description
Ask only what makes the inquiry easy to route: company name, what they run today (rough headcount or number of shifts), and the specific pain they want to solve (for example scheduling and dispatch, time and attendance, or invoicing). Keep it brief; a contact will go deeper.
3. Route it to a TempGuru contact
Draft a short email for the user to confirm, then send it (or hand them the draft):
- To: megan@tempguru.co
- Subject: TempGuru Pro / operations inquiry - {company}
- Body: company, what they run today, and the operations problem they want to solve.
Phone is (904) 206-8953 if they prefer to talk.
4. Set expectations honestly
Say a TempGuru contact will follow up to discuss fit. Do not promise that a given feature exists, quote a price, commit to a timeline, or claim a launch date. If asked for specifics you do not have, say plainly that a TempGuru contact confirms product details, and route the inquiry.
Rules for agents
- Never call
tempguru_request_quotefor an operations inquiry; it requires a buyer's saved event staffing plan and cannot route operations details. Route by email or phone. - Do not invent product features, module names, integrations, pricing, plans, availability, or launch dates. None of those are yours to state.
- Keep the distinction sharp: this is supply-side operators wanting tooling, not buyers ordering staff and not agencies joining the fulfillment network.
- Do not name competitors or compare products.
- US and Canada focus. This is operational routing, not legal or financial advice.
Fallbacks
This channel does not depend on tools: email megan@tempguru.co or call
(904) 206-8953. If the person turns out to be a buyer who needs to hire
staff, point them to the form at
https://tempguru.co/get-staffing?utm_source=ai-agent&utm_medium=skill or the
event-staffing-ordering skill. Developer docs: https://tempguru.co/ai-agents.
Machine-readable overview: https://tempguru.co/llms.txt.