developer-tools Static interface comparison
Apache Pinot MCP Server
4.1.0 5.0.0
1 schema change requires review.No new authority detected.
View the upgrade review as Markdown
A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.
INTERFACE DIFF
What changed, tool by tool
- 4Added tools
- 0Removed tools
- 14Modified tools
- 0Input-schema changes
- 1Output-schema changes
- 0Declared authority changes
18 tools with recorded changes
begin_investigationAddedWhat changed
- New read-only tool begin_investigation.
Why it could matter
- The release adds a capability without declared write authority.
What to verify
- Decide whether agents should be offered this tool.
- Declared effect
- — → read
Input schema
Property Previous (4.1.0) Current (5.0.0) Change (schema root)not present object, additionalProperties=false - Added
baseline_start_msnot present integer, minimum=0required - Added
end_msnot present integer, minimum=0required - Added
profile_idnot present string, maxLength=256, minLength=1required - Added
servicenot present string, maxLength=256, minLength=1required - Added
start_msnot present integer, minimum=0required - Added
Output schema
Property Previous (4.1.0) Current (5.0.0) Change (schema root)not present object - Added
baseline_start_msnot present integerrequired - Added
deadline_secondsnot present integerrequired - Added
end_msnot present integerrequired - Added
max_queriesnot present integerrequired - Added
profile_idnot present stringrequired - Added
run_idnot present stringrequired - Added
scopenot present string, default="single_process_incident_evidence_assembly"optional - Added
servicenot present stringrequired - Added
start_msnot present integerrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
create_schemaModifiedWhat changed
- create_schema: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- PreviousPreview or create a new Pinot schema without replacing an existing schema. The default preview performs strict local structural validation and returns a short-lived confirmation token bound to the exact normalized schema. Pass that token with ``dry_run=false`` to apply. Replacement belongs in ``update_schema``. Failure recovery: Invalid JSON, missing ``schemaName``, and controller validation failures are non-retryable until corrected. Permission failures require access changes; retry transient controller failures only after connectivity is restored.
- CurrentPreview or create a new Pinot schema without replacing an existing schema. The default preview performs strict local structural validation and returns a short-lived confirmation token bound to the exact normalized schema. Pass that token with ``dry_run=false`` to apply. Replacement belongs in ``update_schema``. Failure recovery: Invalid JSON, missing ``schemaName``, and controller validation failures are non-retryable until corrected. Permission failures require access changes; retry transient controller failures only after connectivity is restored.
Input schema
Input schema unchanged.
24 unchanged entries
(schema root)confirmation_tokendry_runschemaschema › dateTimeFieldSpecsschema › dateTimeFieldSpecs › [items]schema › dateTimeFieldSpecs › [items] › dataTypeschema › dateTimeFieldSpecs › [items] › defaultNullValueschema › dateTimeFieldSpecs › [items] › nameschema › dateTimeFieldSpecs › [items] › singleValueFieldschema › dimensionFieldSpecsschema › dimensionFieldSpecs › [items]schema › dimensionFieldSpecs › [items] › dataTypeschema › dimensionFieldSpecs › [items] › defaultNullValueschema › dimensionFieldSpecs › [items] › nameschema › dimensionFieldSpecs › [items] › singleValueFieldschema › metricFieldSpecsschema › metricFieldSpecs › [items]schema › metricFieldSpecs › [items] › dataTypeschema › metricFieldSpecs › [items] › defaultNullValueschema › metricFieldSpecs › [items] › nameschema › metricFieldSpecs › [items] › singleValueFieldschema › primaryKeyColumnsschema › schemaName
Output schema
Output schema unchanged.
13 unchanged entries
(schema root)appliedconfirmation_tokendry_runmessageoperationresource_nameresource_typeresponse_summarystatusverification_toolwarningswarnings › [items]
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
create_table_configModifiedWhat changed
- create_table_config: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- PreviousCreate a new Pinot table configuration. Accepts a typed table-config object. The default ``dry_run=true`` asks Pinot to validate the payload and returns a confirmation token without applying. Failure recovery: Invalid JSON, missing ``tableName``, and controller validation failures need a corrected payload; do not retry unchanged. Fix access failures first, and retry transient controller errors after connectivity is restored.
- CurrentCreate a new Pinot table configuration. Accepts a typed table-config object. The default ``dry_run=true`` asks Pinot to validate the payload and returns a confirmation token without applying. Failure recovery: Invalid JSON, missing ``tableName``, and controller validation failures need a corrected payload; do not retry unchanged. Fix access failures first, and retry transient controller errors after connectivity is restored.
Input schema
Input schema unchanged.
10 unchanged entries
(schema root)confirmation_tokendry_runtable_configtable_config › ingestionConfigtable_config › segmentsConfigtable_config › tableIndexConfigtable_config › tableNametable_config › tableTypetable_config › tenants
Output schema
Output schema unchanged.
13 unchanged entries
(schema root)appliedconfirmation_tokendry_runmessageoperationresource_nameresource_typeresponse_summarystatusverification_toolwarningswarnings › [items]
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
finish_investigationAddedWhat changed
- New read-only tool finish_investigation.
Why it could matter
- The release adds a capability without declared write authority.
What to verify
- Decide whether agents should be offered this tool.
- Declared effect
- — → read
Input schema
Property Previous (4.1.0) Current (5.0.0) Change (schema root)not present object, additionalProperties=false - Added
citationsnot present array, maxItems=64required - Added
citations › [items]not present string - Added
hypothesisnot present anyOf (2), default=nulloptional - Added
reasonnot present anyOf (2), default=nulloptional - Added
run_idnot present string, maxLength=128, minLength=1required - Added
statusnot present string, default="proposed", enum (3)optional - Added
Output schema
Property Previous (4.1.0) Current (5.0.0) Change (schema root)not present object - Added
citationsnot present object, additionalProperties {…}required - Added
confirmed_causenot present boolean, default=falseoptional - Added
dataset_coverage_attestednot present boolean, default=falseoptional - Added
failed_evidence_idsnot present arrayrequired - Added
failed_evidence_ids › [items]not present string - Added
hypothesisnot present anyOf (2)required - Added
hypothesis_validatednot present boolean, default=falseoptional - Added
query_countnot present integerrequired - Added
reasonnot present anyOf (2)required - Added
run_idnot present stringrequired - Added
scopenot present string, default="evidence_assembly_without_rca_semantic_validation"optional - Added
statusnot present string, enum (3)required - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
get_schemaModifiedWhat changed
- get_schema: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousGet one Pinot schema, including dimensions, metrics, time, and primary keys. This is a single-object lookup, not a list, so pagination does not apply. The output preserves additional fields introduced by the connected Pinot version. Failure recovery: For not-found errors, pass the table's exact schema name (normally the table name without a type suffix). Fix permissions before retrying; retry transient controller failures after ``test_connection`` succeeds.
- CurrentGet one Pinot schema, including dimensions, metrics, time, and primary keys. This is a single-object lookup, not a list, so pagination does not apply. The output preserves additional fields introduced by the connected Pinot version. Failure recovery: For not-found errors, pass the table's exact schema name (normally the table name without a type suffix). Fix permissions before retrying; retry transient controller failures after ``test_connection`` succeeds.
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)schema_name
Output schema
Output schema unchanged.
6 unchanged entries
(schema root)dateTimeFieldSpecsdimensionFieldSpecsmetricFieldSpecsprimaryKeyColumnsschemaName
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
get_segment_index_metadataModifiedWhat changed
- get_segment_index_metadata: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousGet per-column index metadata for ONE segment (which indexes each column has). Use this to inspect how a specific segment is indexed (inverted, sorted, range, etc.). Requires a ``segment_name`` from ``list_segments``. For a segment's row count/size/time boundaries use ``list_segment_metadata``; for the table's declared index *configuration* (not per-segment state) use ``get_table_config``. Failure recovery: A missing segment is non-retryable with the same value; refresh ``list_segments`` and use an exact returned name. Retry transient controller errors after ``test_connection`` succeeds.
- CurrentGet per-column index metadata for ONE segment (which indexes each column has). Use this to inspect how a specific segment is indexed (inverted, sorted, range, etc.). Requires a ``segment_name`` from ``list_segments``. For a segment's row count/size/time boundaries use ``list_segment_metadata``; for the table's declared index *configuration* (not per-segment state) use ``get_table_config``. Failure recovery: A missing segment is non-retryable with the same value; refresh ``list_segments`` and use an exact returned name. Retry transient controller errors after ``test_connection`` succeeds.
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)segment_nametable_name
Output schema
Output schema unchanged.
3 unchanged entries
(schema root)columnsindexes
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
get_table_configModifiedWhat changed
- get_table_config: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousGet one table's indexing, retention, tenant, and ingestion configuration. This is a single-object lookup, not a list, so pagination does not apply. Set ``table_type`` only when one side of a hybrid table is needed. Failure recovery: For not-found errors, use an exact name from ``list_tables`` and a valid table type. Fix permissions before retrying; retry transient controller failures after ``test_connection`` succeeds.
- CurrentGet one table's indexing, retention, tenant, and ingestion configuration. This is a single-object lookup, not a list, so pagination does not apply. Set ``table_type`` only when one side of a hybrid table is needed. Failure recovery: For not-found errors, use an exact name from ``list_tables`` and a valid table type. Fix permissions before retrying; retry transient controller failures after ``test_connection`` succeeds.
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)table_nametable_type
Output schema
Output schema unchanged.
4 unchanged entries
(schema root)offlinerealtimetable_name
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
get_table_sizeModifiedWhat changed
- get_table_size: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousGet a table's storage footprint: reported vs. estimated size in bytes. Use this for capacity/size questions about a whole table. It does NOT list segments (use ``list_segments``) or return row counts/time boundaries (use ``list_segment_metadata``). ``reportedSizeInBytes`` is what the servers currently hosting the segments report; ``estimatedSizeInBytes`` assumes every replica is present. Failure recovery: For not-found errors, copy an exact name from ``list_tables``. Fix permission errors before retrying; retry transient controller failures after a health check.
- CurrentGet a table's storage footprint: reported vs. estimated size in bytes. Use this for capacity/size questions about a whole table. It does NOT list segments (use ``list_segments``) or return row counts/time boundaries (use ``list_segment_metadata``). ``reportedSizeInBytes`` is what the servers currently hosting the segments report; ``estimatedSizeInBytes`` assumes every replica is present. Failure recovery: For not-found errors, copy an exact name from ``list_tables``. Fix permission errors before retrying; retry transient controller failures after a health check.
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)table_name
Output schema
Output schema unchanged.
4 unchanged entries
(schema root)estimatedSizeInBytesreportedSizeInBytestableName
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
get_traceAddedWhat changed
- New read-only tool get_trace.
Why it could matter
- The release adds a capability without declared write authority.
What to verify
- Decide whether agents should be offered this tool.
- Declared effect
- — → read
Input schema
Property Previous (4.1.0) Current (5.0.0) Change (schema root)not present object, additionalProperties=false - Added
run_idnot present string, maxLength=128, minLength=1required - Added
trace_idnot present string, maxLength=256, minLength=1required - Added
Output schema
Property Previous (4.1.0) Current (5.0.0) Change (schema root)not present object - Added
columnsnot present arrayoptional - Added
columns › [items]not present string - Added
completenot present boolean, default=falseoptional - Added
dataset_coverage_attestednot present boolean, default=falseoptional - Added
errornot present anyOf (2), default=nulloptional - Added
evidence_idnot present stringrequired - Added
kindnot present stringrequired - Added
metadatanot present objectoptional - Added
metadata › completenessnot present string, default="unknown", enum (3)optional - Added
metadata › early_termination_reasonsnot present array, maxItems=4optional - Added
metadata › early_termination_reasons › [items]not present string, enum (4) - Added
metadata › execution_limit_flagsnot present object, additionalProperties {…}, maxProperties=7, propertyNames {…}optional - Added
metadata › execution_limit_reachednot present anyOf (2), default=nulloptional - Added
metadata › native_query_idnot present anyOf (3), default=nulloptional - Added
metadata › native_statsnot present object, additionalProperties {…}, maxProperties=32optional - Added
metadata › partial_resultnot present anyOf (2), default=nulloptional - Added
metadata › query_sha256not present anyOf (2), default=nulloptional - Added
metadata › request_idnot present anyOf (2), default=nulloptional - Added
metadata › row_limit_reachednot present boolean, default=falseoptional - Added
metadata › servers_queriednot present anyOf (2), default=nulloptional - Added
metadata › servers_respondednot present anyOf (2), default=nulloptional - Added
metadata › unknown_reasonsnot present arrayoptional - Added
metadata › unknown_reasons › [items]not present string - Added
rowsnot present arrayoptional - Added
rows › [items]not present object, additionalProperties=true - Added
run_idnot present stringrequired - Added
sha256not present string, default=""optional - Added
sqlnot present stringrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
list_segment_metadataModifiedWhat changed
- list_segment_metadata: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousGet a deterministic page of segment rows, sizes, and time boundaries. Pinot can return thousands of segment objects. Results are sorted by exact segment name, then sliced with ``limit``/``offset``; follow ``has_more`` until false. Use ``list_segments`` when only names are needed. Failure recovery: An empty page is success. For not-found errors, use ``list_tables``; correct permissions before retrying, and retry transient server failures only after ``test_connection`` succeeds.
- CurrentGet a deterministic page of segment rows, sizes, and time boundaries. Pinot can return thousands of segment objects. Results are sorted by exact segment name, then sliced with ``limit``/``offset``; follow ``has_more`` until false. Use ``list_segments`` when only names are needed. Failure recovery: An empty page is success. For not-found errors, use ``list_tables``; correct permissions before retrying, and retry transient server failures only after ``test_connection`` succeeds.
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)limitoffsettable_name
Output schema
Output schema unchanged.
6 unchanged entries
(schema root)has_moreoffsetreturned_segmentssegmentstotal_segments
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
list_segmentsModifiedWhat changed
- list_segments: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousList a table's segment names, grouped by table type (OFFLINE/REALTIME). Use this to discover segment names — e.g. to get a ``segment_name`` for ``get_segment_index_metadata``, or to see how a table is partitioned. For per-segment row counts / sizes / time boundaries call ``list_segment_metadata`` instead; for total storage call ``get_table_size``. Segment names are paginated (a busy table can have thousands) — use ``limit``/``offset`` and the ``has_more`` flag to page through them. Failure recovery: An empty page is success. For not-found errors, use an exact name from ``list_tables``; correct access errors, or retry transient controller errors.
- CurrentList a table's segment names, grouped by table type (OFFLINE/REALTIME). Use this to discover segment names — e.g. to get a ``segment_name`` for ``get_segment_index_metadata``, or to see how a table is partitioned. For per-segment row counts / sizes / time boundaries call ``list_segment_metadata`` instead; for total storage call ``get_table_size``. Segment names are paginated (a busy table can have thousands) — use ``limit``/``offset`` and the ``has_more`` flag to page through them. Failure recovery: An empty page is success. For not-found errors, use an exact name from ``list_tables``; correct access errors, or retry transient controller errors.
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)limitoffsettable_name
Output schema
Output schema unchanged.
7 unchanged entries
(schema root)OFFLINEREALTIMEhas_moreoffsetreturned_segmentstotal_segments
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
list_tablesModifiedWhat changed
- list_tables: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousList Pinot tables visible to this server (subject to table filters). Returns a paginated list of table names. Use ``limit``/``offset`` and the ``has_more`` flag to page through clusters with many tables. Failure recovery: An empty page is success. For authentication/connectivity errors, verify the controller with ``test_connection`` and retry after access is restored.
- CurrentList Pinot tables visible to this server (subject to table filters). Returns a paginated list of table names. Use ``limit``/``offset`` and the ``has_more`` flag to page through clusters with many tables. Failure recovery: An empty page is success. For authentication/connectivity errors, verify the controller with ``test_connection`` and retry after access is restored.
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)limitoffset
Output schema
Output schema unchanged.
7 unchanged entries
(schema root)has_moreoffsettable_counttablestables › [items]total_tables
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
query_incidentAddedWhat changed
- New read-only tool query_incident.
Why it could matter
- The release adds a capability without declared write authority.
What to verify
- Decide whether agents should be offered this tool.
- Declared effect
- — → read
Input schema
Property Previous (4.1.0) Current (5.0.0) Change (schema root)not present object, additionalProperties=false - Added
candidatenot present anyOf (2), default=nulloptional - Added
kindnot present string, enum (5)required - Added
run_idnot present string, maxLength=128, minLength=1required - Added
Output schema
Property Previous (4.1.0) Current (5.0.0) Change (schema root)not present object - Added
columnsnot present arrayoptional - Added
columns › [items]not present string - Added
completenot present boolean, default=falseoptional - Added
dataset_coverage_attestednot present boolean, default=falseoptional - Added
errornot present anyOf (2), default=nulloptional - Added
evidence_idnot present stringrequired - Added
kindnot present stringrequired - Added
metadatanot present objectoptional - Added
metadata › completenessnot present string, default="unknown", enum (3)optional - Added
metadata › early_termination_reasonsnot present array, maxItems=4optional - Added
metadata › early_termination_reasons › [items]not present string, enum (4) - Added
metadata › execution_limit_flagsnot present object, additionalProperties {…}, maxProperties=7, propertyNames {…}optional - Added
metadata › execution_limit_reachednot present anyOf (2), default=nulloptional - Added
metadata › native_query_idnot present anyOf (3), default=nulloptional - Added
metadata › native_statsnot present object, additionalProperties {…}, maxProperties=32optional - Added
metadata › partial_resultnot present anyOf (2), default=nulloptional - Added
metadata › query_sha256not present anyOf (2), default=nulloptional - Added
metadata › request_idnot present anyOf (2), default=nulloptional - Added
metadata › row_limit_reachednot present boolean, default=falseoptional - Added
metadata › servers_queriednot present anyOf (2), default=nulloptional - Added
metadata › servers_respondednot present anyOf (2), default=nulloptional - Added
metadata › unknown_reasonsnot present arrayoptional - Added
metadata › unknown_reasons › [items]not present string - Added
rowsnot present arrayoptional - Added
rows › [items]not present object, additionalProperties=true - Added
run_idnot present stringrequired - Added
sha256not present string, default=""optional - Added
sqlnot present stringrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
read_queryModifiedWhat changed
- read_query — Output schema: property added: metadata.
- read_query: description changed.
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
- Models choose and call tools partly from their descriptions.
What to verify
- Check consumers of this tool’s output against the new schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousRun a read-only SQL query against Pinot and return a page of rows. Only a single SELECT (or WITH ... SELECT) statement is allowed; the query is rejected if it contains multiple statements or write/DDL/admin keywords. Results are paginated to keep responses small — use ``limit``/``offset`` and the ``has_more`` flag to page through large result sets. Returns ``QueryResult`` with the page of rows, the column list, fetched row count, and a ``has_more`` flag. Failure recovery: SQL/allow-list/permission failures require correcting the query or access; do not retry unchanged. A timeout or connection failure can be retried after ``test_connection`` succeeds. Zero rows is a successful result.
- CurrentRun a read-only SQL query against Pinot and return a page of rows. Only a single SELECT (or WITH ... SELECT) statement is allowed; the query is rejected if it contains multiple statements or write/DDL/admin keywords. Results are paginated to keep responses small — use ``limit``/``offset`` and the ``has_more`` flag to page through large result sets. Returns ``QueryResult`` with the page of rows, the column list, fetched row count, a ``has_more`` flag, and native execution metadata. Missing native metadata is unknown; complete execution does not establish dataset coverage. Failure recovery: SQL/allow-list/permission failures require correcting the query or access; do not retry unchanged. A timeout or connection failure can be retried after ``test_connection`` succeeds. Check ``metadata.completeness`` even for zero rows; no response is promoted to healthy empty evidence.
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)limitoffsetquery
Output schema
Property Previous (4.1.0) Current (5.0.0) Change metadatanot present objectoptional - Added
metadata › completenessnot present string, default="unknown", enum (3)optional - Added
metadata › early_termination_reasonsnot present array, maxItems=4optional - Added
metadata › early_termination_reasons › [items]not present string, enum (4) - Added
metadata › execution_limit_flagsnot present object, additionalProperties {…}, maxProperties=7, propertyNames {…}optional - Added
metadata › execution_limit_reachednot present anyOf (2), default=nulloptional - Added
metadata › native_query_idnot present anyOf (3), default=nulloptional - Added
metadata › native_statsnot present object, additionalProperties {…}, maxProperties=32optional - Added
metadata › partial_resultnot present anyOf (2), default=nulloptional - Added
metadata › query_sha256not present anyOf (2), default=nulloptional - Added
metadata › request_idnot present anyOf (2), default=nulloptional - Added
metadata › row_limit_reachednot present boolean, default=falseoptional - Added
metadata › servers_queriednot present anyOf (2), default=nulloptional - Added
metadata › servers_respondednot present anyOf (2), default=nulloptional - Added
metadata › unknown_reasonsnot present arrayoptional - Added
metadata › unknown_reasons › [items]not present string - Added
10 unchanged entries
(schema root)columnscolumns › [items]has_moreoffsetrow_countrowsrows › [items]total_rowstruncated
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
reload_table_filtersModifiedWhat changed
- reload_table_filters: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- PreviousPreview or apply the configured table-filter YAML without restarting. Reads only the path configured by ``PINOT_TABLE_FILTER_FILE``. The YAML must be an object whose ``included_tables`` value is a non-empty list of glob strings. Allowing every table requires an explicit ``allow_all: true``. The default ``dry_run=true`` validates and reports the before/after patterns and returns a short-lived confirmation token. Pass ``dry_run=false`` with that token to apply the exact candidate atomically. Editing the file after preview invalidates the confirmation and requires another preview. Returns: Preview/application status, whether it was applied, old/new patterns, and a confirmation token on previews. Failure recovery: A missing setting/file or malformed YAML is non-retryable until corrected; fix ``PINOT_TABLE_FILTER_FILE`` or its ``included_tables`` list, then retry.
- CurrentPreview or apply the configured table-filter YAML without restarting. Reads only the path configured by ``PINOT_TABLE_FILTER_FILE``. The YAML must be an object whose ``included_tables`` value is a non-empty list of glob strings. Allowing every table requires an explicit ``allow_all: true``. The default ``dry_run=true`` validates and reports the before/after patterns and returns a short-lived confirmation token. Pass ``dry_run=false`` with that token to apply the exact candidate atomically. Editing the file after preview invalidates the confirmation and requires another preview. Failure recovery: A missing setting/file or malformed YAML is non-retryable until corrected; fix ``PINOT_TABLE_FILTER_FILE`` or its ``included_tables`` list, then retry.
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)confirmation_tokendry_run
Output schema
Output schema unchanged.
9 unchanged entries
(schema root)appliedconfirmation_tokenmessagenew_filter_countnew_filtersprevious_filter_countprevious_filtersstatus
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
test_connectionModifiedWhat changed
- test_connection: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousProbe Pinot connectivity and return diagnostics. Runs three checks — broker connection, a trivial ``SELECT 1`` query, and a controller table listing — and reports which succeeded plus a small sample of tables. Useful for troubleshooting configuration before using other tools. Failure recovery: Individual check failures are returned in ``error``. Verify the broker and controller URLs, credentials, and network, then retry only failed checks.
- CurrentProbe Pinot connectivity and return diagnostics. Runs three checks — broker connection, a trivial ``SELECT 1`` query, and a controller table listing — and reports which succeeded plus a small sample of tables. Useful for troubleshooting configuration before using other tools. Failure recovery: Individual check failures are returned in ``error``. Verify the broker and controller URLs, credentials, and network, then retry only failed checks.
Input schema
Input schema unchanged.
1 unchanged entry
(schema root)
Output schema
Output schema unchanged.
9 unchanged entries
(schema root)connection_testdbapi_testerrorquery_testsample_tablessample_tables › [items]tables_counttables_test
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
update_schemaModifiedWhat changed
- update_schema: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- PreviousUpdate an existing Pinot schema. Accepts a typed schema object. This can change column definitions on a live table; the default ``dry_run=true`` previews without applying and returns a confirmation token bound to the exact replacement. Failure recovery: Invalid JSON/name or schema validation failures require a corrected payload; do not retry unchanged. Fix permission errors first, and retry transient controller failures only after connectivity is restored.
- CurrentUpdate an existing Pinot schema. Accepts a typed schema object. This can change column definitions on a live table; the default ``dry_run=true`` previews without applying and returns a confirmation token bound to the exact replacement. Failure recovery: Invalid JSON/name or schema validation failures require a corrected payload; do not retry unchanged. Fix permission errors first, and retry transient controller failures only after connectivity is restored.
Input schema
Input schema unchanged.
26 unchanged entries
(schema root)confirmation_tokendry_runreloadschemaschema › dateTimeFieldSpecsschema › dateTimeFieldSpecs › [items]schema › dateTimeFieldSpecs › [items] › dataTypeschema › dateTimeFieldSpecs › [items] › defaultNullValueschema › dateTimeFieldSpecs › [items] › nameschema › dateTimeFieldSpecs › [items] › singleValueFieldschema › dimensionFieldSpecsschema › dimensionFieldSpecs › [items]schema › dimensionFieldSpecs › [items] › dataTypeschema › dimensionFieldSpecs › [items] › defaultNullValueschema › dimensionFieldSpecs › [items] › nameschema › dimensionFieldSpecs › [items] › singleValueFieldschema › metricFieldSpecsschema › metricFieldSpecs › [items]schema › metricFieldSpecs › [items] › dataTypeschema › metricFieldSpecs › [items] › defaultNullValueschema › metricFieldSpecs › [items] › nameschema › metricFieldSpecs › [items] › singleValueFieldschema › primaryKeyColumnsschema › schemaNameschema_name
Output schema
Output schema unchanged.
13 unchanged entries
(schema root)appliedconfirmation_tokendry_runmessageoperationresource_nameresource_typeresponse_summarystatusverification_toolwarningswarnings › [items]
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
update_table_configModifiedWhat changed
- update_table_config: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- PreviousUpdate an existing Pinot table configuration. Accepts a typed replacement table-config object. This changes a live table; the default ``dry_run=true`` asks Pinot to validate it, compares it with the current configuration, and returns a token without applying. Failure recovery: Invalid JSON/name or controller validation failures require a corrected payload; do not retry unchanged. Fix access errors first, and retry transient controller failures only after connectivity is restored.
- CurrentUpdate an existing Pinot table configuration. Accepts a typed replacement table-config object. This changes a live table; the default ``dry_run=true`` asks Pinot to validate it, compares it with the current configuration, and returns a token without applying. Failure recovery: Invalid JSON/name or controller validation failures require a corrected payload; do not retry unchanged. Fix access errors first, and retry transient controller failures only after connectivity is restored.
Input schema
Input schema unchanged.
11 unchanged entries
(schema root)confirmation_tokendry_runtable_configtable_config › ingestionConfigtable_config › segmentsConfigtable_config › tableIndexConfigtable_config › tableNametable_config › tableTypetable_config › tenantstable_name
Output schema
Output schema unchanged.
13 unchanged entries
(schema root)appliedconfirmation_tokendry_runmessageoperationresource_nameresource_typeresponse_summarystatusverification_toolwarningswarnings › [items]
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
No tools match these filters.
Evidence and provenance
- Static findings
- REVIEW from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
- Human review
- Pending human review. No reviewer decision is recorded for this comparison.
- Published evidence
- Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
- Comparison
startreedata-mcp-pinot/4.1.0~5.0.0The published comparison identifier.- Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 16, 2026, 10:19 PM UTC.- Distribution
pypi- Previous release
mcp-pinot-server@4.1.014 tools · published by the registry Aug 29, 2026, 10:35 PM UTC · upstream 4.1.0Artifact integritysha256-GTiypEKjTwJ2SZJzdoB0d51W1Xdoyb6FjNbXKUApX4Y=Artifactmcp_pinot_server-4.1.0-py3-none-any.whlInterface fingerprintsha256:f24ed68635de0fabb39d1439292c5afd0fecd0680f200abcbe56ed5bfd67d75cExact interface snapshot (JSON)- Current release
mcp-pinot-server@5.0.018 tools · published by the registry Oct 12, 2026, 12:58 AM UTC · upstream 5.0.0Artifact integritysha256-+unWJw6pCILWbzuApVkHwg2H4bqO8jzBzBKG2DRZH5Q=Artifactmcp_pinot_server-5.0.0-py3-none-any.whlInterface fingerprintsha256:de53328f47de20f4687f6afb0a327f5041b46721ccb08911aa62bb8fbceddb2fExact interface snapshot (JSON)- Comparison record
- Exact comparison record (JSON)
The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.
MODELARA ANALYSIS OUTPUT
Interface findings
Requires review
1 findingread_queryREVIEWChangedShow details
output property added: metadata
Informational
18 findingsbegin_investigationINFOAddedfinish_investigationINFOAddedget_traceINFOAddedquery_incidentINFOAddedcreate_schemaINFOChangedcreate_table_configINFOChangedget_schemaINFOChangedget_segment_index_metadataINFOChangedget_table_configINFOChangedget_table_sizeINFOChangedlist_segment_metadataINFOChangedlist_segmentsINFOChangedlist_tablesINFOChangedread_queryINFOChangedreload_table_filtersINFOChangedtest_connectionINFOChangedupdate_schemaINFOChangedupdate_table_configINFOChanged
What do these results mean?
- PASS
- No policy-significant interface change detected.
- REVIEW
- Interface changes require inspection.
- FAIL
- A policy-significant change was detected.
- INVALID
- The comparison could not be evaluated reliably.