Integration Tools
Integration tools help your AI assistant understand how systems connect. They surface API contracts, database schemas, event producers and consumers, configuration keys, and authentication policies - giving the assistant a complete picture of how your application integrates with its dependencies.
api_contract_fetch
Section titled “api_contract_fetch”Get API contract definitions extracted from OpenAPI and Swagger specifications in your codebase. Returns endpoint paths, methods, request/response schemas, and parameter definitions.
Parameters
Section titled “Parameters”| Name | Type | Required | Description |
|---|---|---|---|
workspace_id |
string | No | Limit results to a specific workspace |
repo_id |
string | No | Limit results to a specific repository |
endpoint |
string | No | Filter by endpoint path (e.g. /users) |
Example prompt
Section titled “Example prompt”“Show me the API contract for /users endpoints”
The assistant calls api_contract_fetch with the endpoint filter and returns the matching API definitions including HTTP methods, request parameters, response schemas, and any documentation from the spec.
schema_browser
Section titled “schema_browser”Browse database schema definitions extracted from SQL DDL files and migration scripts. Returns table structures, column types, constraints, indexes, and relationships.
Parameters
Section titled “Parameters”| Name | Type | Required | Description |
|---|---|---|---|
table_name |
string | No | Filter by table name |
workspace_id |
string | No | Limit results to a specific workspace |
repo_id |
string | No | Limit results to a specific repository |
Example prompt
Section titled “Example prompt”“What columns does the users table have?”
The assistant calls schema_browser with the table name and returns the complete table definition including column names, data types, constraints (NOT NULL, UNIQUE, PRIMARY KEY), default values, and foreign key relationships.
event_catalog
Section titled “event_catalog”Explore event producers and consumers in your codebase. Returns which components emit events, which components subscribe to them, and the event payload structures.
Parameters
Section titled “Parameters”| Name | Type | Required | Description |
|---|---|---|---|
event_name |
string | No | Filter by event name |
direction |
string | No | producers (who emits) or consumers (who handles) |
workspace_id |
string | No | Limit results to a specific workspace |
repo_id |
string | No | Limit results to a specific repository |
Example prompt
Section titled “Example prompt”“What events does the OrderService produce?”
The assistant calls event_catalog with the direction filter and returns a list of events emitted by the service, including event names, payload types, and the code locations where they are published.
config_resolver
Section titled “config_resolver”Look up configuration keys and their sources. Returns where configuration values are defined, where they are consumed, and any default values or environment variable mappings.
Parameters
Section titled “Parameters”| Name | Type | Required | Description |
|---|---|---|---|
key |
string | No | Filter by configuration key name |
workspace_id |
string | No | Limit results to a specific workspace |
repo_id |
string | No | Limit results to a specific repository |
Example prompt
Section titled “Example prompt”“Where is the database URL configured?”
The assistant calls config_resolver and returns the configuration key definitions, the files where they are set (property files, YAML, environment variables), and the code locations where they are read.
auth_policy_map
Section titled “auth_policy_map”Map authentication and authorization policies across your codebase. Returns which endpoints require authentication, what roles or permissions are checked, and how auth middleware is applied.
Parameters
Section titled “Parameters”| Name | Type | Required | Description |
|---|---|---|---|
workspace_id |
string | No | Limit results to a specific workspace |
repo_id |
string | No | Limit results to a specific repository |
Example prompt
Section titled “Example prompt”“What auth is required for the admin endpoints?”
The assistant calls auth_policy_map and returns a mapping of endpoints to their authentication requirements - which routes are public, which require a valid token, and which enforce specific roles or permissions.