MCP example prompts
Read first, inspect drafts and check actual outcomes.
Try these jobs after setup. The client must use live schemas and distinguish an answer/proposal from an actual record change.
Read the business
Read today’s business overview from Era. Separate enabled modules,
ready sources and waiting work. Do not change records.era_overview is a useful start. A ready source can still hit quota/access limits on a later call.
Find customers
Find Demo customers. Make a table of identities, contact details and status.
Do not search another workspace; state explicitly if more pages remain.Inspect records_find results using identities. More than one person can have the same name.
Research sourced knowledge
Search memory for delivery terms and cite each important claim.
Show conflicting sources instead of silently treating one as correct.Read brain_search snippets and sources; a graph edge alone does not validate a claim.
Prepare a quote draft
Draft a quote for my selected Demo customer using my supplied lines.
Show amounts and tax details; do not send it to the customer.document_create writes; choose customer identity and lines using its schema. document_issue separately sends/issues and waits for applicable approval.
Save an output
Save these results to Era Files as CSV.
Report the file ID and whether the upload has actually completed.Save with file_save and obtain download information with file_get. Do not call the first page the whole dataset; finish returned upload steps for large files.
Check the outcome
“Waiting for approval”, “partial” and “done” differ. Inspect the call result or turn_report; do not request a completed write again.
Tool groups
Learn which tools support these jobs.