Tools and workflows

Understand which Finbar tools your assistant calls and how they work together.


Once you connect Finbar, describe the research task in your conversation. The assistant chooses tools, passes arguments and reads the results. You do not need to write HTTP requests or manage access tokens.

A tool is a named operation, such as list_documents. Its arguments are the inputs it needs, such as the company's entity_id. The tool names below also help you understand the calls shown in your assistant's activity log.

Company and document tools

ToolMain argumentsResult
search_entityq: company name or tickerMatching companies and their entity_id values
get_entityentity_idCompany information and identifiers
list_documentsentity_id; optional document types and period boundsReports, their periods and document_id values
search_documentquery and exactly one of entity_id or document_idMatching paragraphs and tables with item IDs and previews
read_documentitem_id, or document_id with start_index and limitParagraph or table content
get_market_dataentity_id; optional range of 2y or maxAvailable price history and market information

A company record is called an entity. A document item is a paragraph or table within a report. The assistant should use the IDs returned by earlier calls, rather than guess them from a company name or report title.

Research a disclosure

The typical sequence is:

  1. search_entity finds the company ID.
  2. list_documents identifies the relevant reports.
  3. search_document locates matching paragraphs or tables.
  4. read_document reads the source content behind the search previews.

A preview is a short excerpt. Reading the source gives the assistant more context for its answer. Ask it to retain document and item IDs so that you can trace claims back to their sources.

Financial dataset tools

ToolMain argumentsResult
get_datasetentity_idThe current published dataset's ID and metadata
get_dataset_catalogueentity_id; optional expected_dataset_idAvailable metrics, reporting groups, company scopes and periods
query_datasetentity_id, metric_ids, scope_combinations, periodsSelected financial values and available source references

The catalogue is the list of financial series you can query. It is needed because metric definitions and company reporting structures vary. See metrics, series and scopes for the data model and reporting periods for fiscal-year conventions.

Retrieve financial history

The assistant should discover the dataset and catalogue before calling query_dataset. It should copy the catalogue's IDs and complete scope paths, and select quarterly periods using their durations.

Dataset query arguments follow the same selection structure as the REST query body, with entity_id added as a tool argument. expected_dataset_id detects publication changes; value_version selects original or latest restated observations.

To check a returned number, ask the assistant to pass its source item_id to read_document. Values and sources explains the result fields.

Results that need more calls

Tool results are bounded, so one call may not contain all matches or all of a report. If a result contains next_cursor, the assistant can repeat the call with that string as cursor, keeping the same target and selections. A cursor is a continuation value; it should be copied unchanged.

Document reads return at most 10 chunks per call. For subsequent document windows, use cursor instead of start_index and keep limit. If is_truncated is true, some returned content was shortened. A table can be read in a smaller range using table_subslice, for example R0C0:R4C3 for rows 0–4 and columns 0–3.

Tool errors

A failed tool call returns an error with a code, message and request_id. The assistant should use the code to decide what to do next.

CodeNext step
validation_failedCorrect the tool arguments using the returned field issues
unauthenticatedReconnect to Finbar
insufficient_scopeCheck the connection's requested permissions
not_foundCheck the ID and whether the data is available to your account
dataset_changedFetch the current dataset and catalogue, then rebuild the query
rate_limit_exceededWait for retry_after_seconds before another call
service_unavailable, internal_error, gateway_timeoutRetry the read after a delay

A prompt can trigger several calls, each using your account's shared request allowance. For a persistent failure, send the request ID and tool name to Finbar support.