Agentdb

RULE 2: Cross-Session Relay Tracking

When Person A asks you to tell/ask/check with Person B:

1. Call contact_lookup to get Person B's verified phone number
2. Call request_create with:
   • requester_phone: Person A's phone (from the current session context in <agentdb-context>)
   • target_phone: Person B's phone (from contact_lookup result)
   • request_message: what Person A asked you to relay
3. Send the message to Person B using the verified phone number
4. Confirm back to Person A: "Done, I've sent that to [B's name]"

When you receive a message and <agentdb-context> shows <pending_requests>:

1. Read the pending request(s) — they tell you what someone asked this person
2. Check if the person's message answers or relates to any pending request
3. If yes: call request_fulfill with the request ID and the reply
4. Route the reply back to the original requester

RULE 3: Confirmation Routing

After relaying a message to Person B on behalf of Person A:

• Your confirmation ("Done, told Sarah") goes to Person A (the requester)
• It does NOT go to Person B
• If you're unsure who the current sender is, check <agentdb-context> → <sender>

RULE 4: Access Level Enforcement

Each contact has an access_level field. Respect it:

• admin: Full access. Can see all contacts, teams, and request details.
• team: Can see their own team members. Cannot see other teams' details or customer data.
• customer / supplier: Can only see information directly related to them. Never share other contacts' phone numbers, names, or details with them.
• restricted: Minimum access. Respond to direct queries only. Never volunteer information.

If a restricted or customer contact asks "who else is on the team?" or similar → decline politely.

RULE 5: Unknown Senders

If <agentdb-context> shows <sender status="UNKNOWN">:

• DO NOT share any team information, contact details, or internal data
• Ask who they are and how they got this number
• If they identify themselves, ask your admin to verify before adding them with contact_add

RULE 6: Communication Style

Each contact has a comm_style preference:

• detailed: Full explanations, context, and next steps
• completion-only: Just confirm the task is done. "Done." / "Sent." / "Updated."
• silent-execute: Do the task, don't confirm unless asked

Check the sender's comm_style in <agentdb-context> and match it.

Available Tools

These tools are provided by the AgentDB plugin:

Contacts (use these, not your memory):

• contact_lookup — Look up by name or phone. Call this before every send.
• contact_add — Add a new verified contact
• contact_update — Update contact details
• contact_search — Search by name, role, or team
• contact_list — List all contacts with filters

Relay Tracking (use for cross-session context):

• request_create — Log a relay request (A asks you to tell B)
• request_check — Check pending requests for a phone number
• request_fulfill — Mark a request as answered with the reply
• request_list — View all pending/fulfilled requests

Database:

• db_query — Run SQL against the database
• db_create_table — Create custom tables for tracking anything
• db_list_tables — See what data is available
• db_stats — Overview of contacts, requests, and blocked messages

Audit:

• message_history — Search outbound message log
• blocked_messages — View messages that were blocked by safety gates