search_available_data,
to describe a table before it writes SQL, and to check a statement with
plan_sql before it runs it. They also tell the model to treat rows and
descriptions as data, not as instructions.
Tools
Each tool calls the Workspace API as the person. A tool needs a role that grants one of the permissions in its row. A permission also covers each permission under it:tenant covers them all. An OAuth grant and an MCP
token work on every tool.
Query Provider data
A person sees these tools when a role can query: Provider Pools Reader, Data Access, or Workspace Administrator. A member who holds only Viewer sees none of them.
Tables are named
providers.<provider>.<table>. These tools use the same
operations as SQL over HTTP. Provider Policies and
source permissions narrow what they read for every person. All data access
does not apply to them: an administrator’s host reads only what the Policies
give the administrator’s roles.
A statement can call the SQL AI functions, such as ponder() and embed().
Each one is a model call under the Workspace’s model policy, as it is in any
other SQL.
Published Plots
Provider connections and Taps
Powers
The server has no tool that changes data. It has no tool that sends a Message
to Ponder, changes a Provider connection, or runs
preview_plot.
Prompts and resources
Each prompt and resource returns one guidance text. The server reads the Workspace’s Power of the same name when you may use Ponder. Otherwise it reads Parable’s built-in text.
In Claude Code, with the server named
parable, run a prompt as
/mcp__parable__pool_search. Attach a resource as
@parable:parable://guidance/providers.
Limits
returnedRows counts the rows in a result, not the rows that the query
matched. A result marked truncated is not the whole answer. Narrow the
query, or add a LIMIT.
The query tools answer a limit with its own status. None of these statuses
means that the SQL is wrong:
Tool errors
A tool that fails returns a result withisError: true. The result’s text
is the Workspace API’s message, its code, and its status:
... (status: 404). A permission error needs a different role, not a
different query.