Edyn

edyn MCP system status

Use to check which edyn data connectors and read capabilities are currently available. Do not use to retrieve operational or personal data. Never returns credentials or secret configuration.

Find an edyn person

Use first when you need a stable edyn identity for a carer, client, employee, or lead. Searches authorised sources and returns candidates with confidence and provenance. Do not assume same-name records are the same person; ambiguous candidates remain separate. Requires person.read.

Get a carer overview

Use after find_person when a broad, cross-system picture of one carer is needed. Requires a canonical carerId, aggregates authorised profile, onboarding, compliance, training, availability, placement, document and activity data, and reports missing sources or discrepancies. Do not use for clients or name searches. Sensitive fields require additional permissions.

Count carers by Airtable status

Use for aggregate recruitment and compliance questions such as "How many carers are Compliance attentive?" Reads only the two approved Airtable status fields and returns counts, never names or record IDs. Use field=compliance for values such as "Compliance attentive", field=application for funnel values such as "Compliance - Attentive", or field=both if the request is ambiguous. Requires carer.read and carer.compliance.read.

Cross-tabulate carer statuses

Use for filtered cross-status questions such as "For carers whose compliance status is Non compliant, show the application status breakdown." Filters one approved Airtable status field by an exact value and groups the matching cohort by the other status field. Returns counts only, never names or record IDs. Requires carer.read and carer.compliance.read.

Analyse carer onboarding bottlenecks

Use for aggregate questions about which onboarding or compliance items affect active non-compliant carers most often. Returns counts, percentages, mapped responsibility and a compliance-status breakdown, never names or record IDs. Conditional workflows such as DBS, right-to-work and references are reported as mixed unless their detailed linked status is available. Timing metrics are explicitly unavailable until item-level timestamps are mapped. Requires carer.read and carer.compliance.read.

Get deterministic carer onboarding status

Use for a canonical carerId to understand onboarding blockers. Deterministically separates actions the carer must take from edyn work and checks already processing with third parties, so a carer is not chased for processing items. Requires carer.read and carer.compliance.read. Do not use for general profile questions.

Get outstanding carer actions

Use with a canonical carer ID to retrieve deterministic action groups: required from the carer, required from edyn, waiting on a third party, and completed recently. It is read-only and does not send reminders or update systems. The initial prototype supports entityType=carer only. Requires carer.read and carer.compliance.read.