add_dictionary_entry
Map coded column values to their business meanings, enabling natural language understanding of database content.
Instructions
Map a coded column value to its business meaning (e.g. stage '1' -> 'Performing').
Use so grounding and generation can interpret enum-like codes. Requires the connection to be introspected first so the column can be resolved. Returns the new entry's id.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"connection": "<connection>",
"table_name": "<table_name>",
"column_name": "<column_name>",
"raw_value": "<raw_value>",
"display_value": "<display_value>"
},
"name": "add_dictionary_entry"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| connection | Yes | Target database connection — its name or id (case-insensitive). List the available connections with list_connections. | |
| table_name | Yes | Table containing the column (must already be introspected). | |
| column_name | Yes | Column whose coded value you are explaining. | |
| raw_value | Yes | The stored/coded value as it appears in the column (e.g. '1'). | |
| display_value | Yes | The business meaning of that value (e.g. 'Performing'). | |
| description | No | Optional extra explanation of the value. |