Useful tools.
Clear boundaries.

Try it with an agent

This example exposes three authenticated agent tools: list the five examples, evaluate a record, and prepare a portable review packet. They use the same deterministic rules as the page. No live language model or external business account is connected.

In Codex, the site owner can connect the LongSpoke plugin provisioned by Sites. In Claude, use a supported MCP connection where your account and administrator permit it. Connection availability and authentication depend on the client. The endpoint supports MCP 2026-07-28 discovery and legacy clients from 2025-06-18; older clients need an update.

Use this hosted endpoint in your MCP client. Authentication is required; the custom website domain does not provide the agent endpoint.

https://longspoke.cronk-compan-0693.chatgpt.site/mcp

A useful starting request:

Open the LongSpoke supplier invoice example. Explain the receiving exception, show the source evidence, and stop for my review before preparing a packet.

Tool arguments can record a demo review decision. That is supplied input, not proof that a second person approved it. These tools have no email, invitation, accounting or Microsoft write capability.

What runs here

Five fictional records, editable working values, deterministic checks, a review decision, and JSON, CSV, Markdown or print outputs. Drafts and recent events stay in this browser. Role views show how a team workflow could feel; they do not invite or authenticate another person.

After a successful online visit, the public shell can be stored for offline use. Check the offline message at the bottom of the page. Local storage can be cleared or evicted by your browser; keep a downloaded packet when the record matters.

What a client system adds

A scoped build can add real extraction and AI reasoning, company-specific rules, authenticated reviewers, connected data and an agreed destination. API access, permissions, licensing, recovery and audit needs are checked against the actual systems.

Microsoft 365, a custom application and a native mobile experience are different delivery choices. Offline capture is designed for the chosen platform. A browser-based Power App does not provide native offline capability.

New technology is evaluated, tested and introduced when it improves the work. The service scope and update plan are agreed together.

Your example data

No uploads, analytics trackers or contact forms are used by this example. Working drafts are stored locally. Agent tool inputs are processed by the hosting service and returned to the caller; the application does not save them to a server database. Hosting and client providers may maintain their own operational logs. Use fictional values only.