Agent Maple

Get Project Update

Get a broad Daily Logs-backed update for a project or site over a reporting window. Use focused Daily Logs queries or record detail for one specific record. Broad project or site update from recorded Daily Logs, not focused record detail. Read-only, source-backed update with no project-model interpretation.

List Access Requests

Read the people waiting on a decision about taking part in this project -- the ones the screen calls Pending. This is the console's approvals screen; it is not part of recording a check-in. Pass a status to read the ones already approved or denied. Which requests to read. Defaults to the ones nobody has decided yet. **Reading these requires an administrator role**, and the operation refuses otherwise. A request carries the person's own submitted details and a count of records nobody has releas

Approve Access Request

Approve one person's request to take part in this project, optionally correcting the role or company they typed. This puts them on the project and releases every record of theirs that was waiting on the decision. Approve one request, optionally correcting what the person typed. `role` and `company_name` replace the submitted values on this decision only; the submitted values are kept as they were, so the correction stays visible. **Leaving a field out and sending it empty mean different thing

Deny Access Request

Deny one person's request to take part in this project. A reason is required and is kept on the request for the administrators who read it later. Their records are kept and stay marked; nothing is deleted, and approving them afterwards releases the same records in one action. Deny one request. The reason is required and is kept on the request. It is written for the administrators who read the request later, not for the person: they are told only that the request was not approved, and nothing a

Record Check In

Record that the person you are talking to is on site today — 'here', 'checking in', 'on site, north tower'. One message often carries more than the check-in: a location, an hours value, named crew, or a headcount; pass all of it in one call. Partial information is valid — '4 guys, names tomorrow' is a headcount with no names. When the person names others, call list_project_people first and match the names against that roster yourself. To change an earlier check-in ('actually Dave went home at 10

List Project People

List the project's known people. Call this before passing named_people to record_check_in — matching the user's wording against the list is your job, not the tool's. A name that fits exactly one person resolves; two Daves means you ask which; a name that fits nobody is confirmed with the user and passed with create_new_person=true. No arguments; the project comes from the caller's context.

Attendance For Day

Read a project's attendance for one day, grouped by company. This is the console's attendance screen; it is not part of recording a check-in. Which day, and whether held rows are wanted. `date` defaults to today in the project's timezone. `include_held` defaults to false: a held record is invisible to every read path that does not ask for it, and this is the only argument in the product that asks. **Asking requires an administrator role**, and the operation refuses otherwise. Held rows belong

Record Daily Log Entry

Record exactly one atomic thing that happened on site today (or a given date): manpower, activities, visitors, inspections (incl. FLHA), deliveries, incidents, blockers, notes, photos, weather. If a user message contains multiple distinct activities, crews, companies, or log items, call this tool separately for each item; never combine them or drop later items. Manpower entries require a company: call list_project_companies first, match what the user said against that list yourself, and pass the

Query Daily Logs

Read daily-log entries for a project from Agent Maple's records: what happened on a day or in a date range, filtered by entry type, submitter, or company. Use daily_log_summary instead for counts/rollups like 'who submitted today?'. Read daily-log entries from Agent Maple's own records (never live Procore). Days (containers) in the range, newest first, with their entries.

Daily Log Day Detail

Open one specific day's daily log for a project: the day container and every entry recorded for that date, with each entry's submitter, provenance, and sync status. Use this to drill into a single day; use query_daily_logs for a range or a filtered search across days. Open one day's daily log — the container and all its entries — by date. One day's daily log with its entries. found=false when nothing was logged that day, so the caller can render an empty state rather than an error.

Daily Log Summary

Aggregate daily-log stats for a project over a date range (default today): entry counts by type, who submitted and how many, how many synced to Procore. The right tool for 'who submitted logs today?' and dashboard-style rollups. Aggregate stats — 'who submitted logs today?', dashboard cards. Counts by type and submitter over the range, from AM records only.

List Project Companies

List the project's companies. Call this before recording manpower entries — record_daily_log_entry expects company_name to be one of these names, and matching the user's wording against the list is your job, not the tool's. Companies sync from Procore's directory when the project is connected; only a company from that sync carries the Procore vendor that puts a company on the Procore manpower log. List the project's company reference list (for resolving manpower companies). The project's compa