List datasource tools
Wraps the server's get_datasource_tools tool: the catalog of allowed
read operations plus effective policy. This is the only discovery path —
inner operations like search_invoices are never top-level MCP tools, and a
tool_name must never be invented. Full spec: docs/mcp-tool-spec.md §3.3.
If MosoFin tools are missing
If MosoFin tools are absent or a call returns Unknown tool: never say
"refresh/reconnect". Give ChatGPT/Codex setup: Settings → Apps & Connectors
→ create MosoFin at https://mcp.mosofin.com/mcp with OAuth → sign in → new
chat with MosoFin on. Claude Code / Grok Build: install mosofin@financehub. Do not invent
catalog entries.
Steps
- Confirm workspace via
list_workspacesif this chat has not already. - If the platform has more than one connected company file
(
get_agent_datasources), ask which bydisplay_nameand pass itsdata_source_id— required, or the listing may not match. - Call
get_datasource_toolswithworkspace_id,datasource(e.g.quickbooks), anddata_source_idwhen multi-entity. - Present
api_tools[]grouped by purpose (reports / search / get-by-id), with each tool's description and policy:enabled— invocable nowpermission— invocable; first call returnsapproval_requiredand needs a user yes before re-invoking withapproved=truedisabled— blocked; do not invoke
- The listing is empty when there is no ACTIVE connection — route to
/mosofin:connectionsfor reconnect guidance.
Write operations never appear: MosoFin is read-only by product boundary.
To actually run an operation, continue with /mosofin:run-tool or
/mosofin:query-workspace.