Data Dolphin

Use this before any write tool when you need a read-only proposal for what to enrich next. It lightly composes upstream search, agent-package, and optional implementation-context without creating drafts.

build_enrichment_proposal

Use this to retrieve a read-only API contract context package for one project, preferably by `operation_id` when known. It assembles upstream API metadata only and must not be treated as sync, import, or publication logic.

get_api_contract_context

Use this when a general-purpose agent needs upstream-curated project context and operational_package guidance. Read operational_package before planning changes, and implement only upstream items marked actionability=actionable.

get_agent_package

Use this when a coding agent needs an upstream-assembled implementation package for one project. Provide `goal` when it helps upstream prioritize relevant context.

get_implementation_context

Use this when you already know `project_key` and need upstream project context. Prefer enabling only the include flags you actually need to keep the response smaller.

get_project

Use this before modeling a new BootstrapProject. It returns the official upstream project creation patterns, lifecycle defaults, project key rules, and validation checklist. This tool is read-only and never creates a project.

get_project_creation_context

Use this only when you already know both keys and need the current sanitized document body. Prefer discovery or search tools first if you are still exploring.

get_project_document

Use this to inspect the current agent instructions for one project before composing new guidance or draft updates.

list_agent_instructions

Use this to inspect the current business rules for one project before proposing or drafting rule changes.

list_business_rules

Use this to inspect read-only HTTP endpoints derived from imported code for one project. Prefer repository or service filters to keep the response narrow and reduce stale-context ambiguity.

list_code_endpoints