Tools
The Entropy Data MCP server exposes the following 35 tools.
Data Product Discovery
Get Data Product Details fetch
Get a data product by its ID. The data product contains all its output ports and server information. The response includes access status for each output port and inlines any data contracts.
- Name
dataProductId- Type
- string
- Description
The data product ID
Search Data Products search
Find and explore data products in the organization. Parameter:
- query: Keywords to search for in data product names/descriptions. Optional, use "*" to get all data products. Returns a list of data products with basic information, sorted by certification level (highest first). Includes certification name and rank if certified. You can fetch details later.
Strategy: First use a generic search term like "sales", "customers", "marketing" to find relevant data products. Use a more specific term if the results are too broad.
- Name
query- Type
- string
- Description
Keywords to search for in data product names/descriptions
Access Management
Request Data Product Access request_access
Submit an access request for a specific data product's output port. This creates a formal request that may be automatically approved or require manual approval.
Parameters:
- dataProductId: The ID of the data product to request access to
- outputPortId: The ID of the output port within the data product
- purpose: Business justification for accessing the data
- roles: Optional list of role names to request (e.g., ["analyst", "data_engineer"]). Available roles can be found in the data contract's roles section, if any.
- useCaseId: Optional id of the use case the request serves. Some organizations require one; a request without it is then refused with a message that lists the ids of the use cases that can be cited.
Returns information about the created access request including its ID, status, approval status, and requested roles.
- Name
dataProductId- Type
- string
- Description
The ID of the data product
- Name
outputPortId- Type
- string
- Description
The ID/name of the output port to request access to
- Name
purpose- Type
- string
- Description
Business justification for accessing the data. Use a high-level description that will be used to validate purpose. If there is a data contract, the purpose must be in line with the terms specified in the data contract.
- Name
roles- Type
- array
- Description
Optional list of role names to request access for. Available roles are defined in the data contract.
- Name
useCaseId- Type
- string
- Description
Optional id of the use case this request serves. Required where the organization asks every access request to cite a use case; a request without one then returns the ids of the use cases that can be cited.
Check Access check_access
Check whether a query on a data product's output port would be allowed, without running it. The decision is the same one execute_query makes: an active access agreement, and the query checked against the data contract's terms of use for the purpose of your access agreement. You can't supply another purpose here.
Parameters:
- dataProductId: The ID of the data product
- outputPortId: The ID of the output port
- query: The SQL query you intend to run
Returns whether the query would be allowed and, if not, why.
- Name
dataProductId- Type
- string
- Description
The ID of the data product
- Name
outputPortId- Type
- string
- Description
The ID / name of the output port
- Name
query- Type
- string
- Description
The SQL query you intend to run
Query Execution
Execute SQL Query execute_query
Execute SQL queries on data product output ports and query results as structured data (limited to 100 rows). Supports: Databricks, PostgreSQL, BigQuery, Snowflake, MySQL, MariaDB, SQL Server (MSSQL), Exasol, Trino, Dremio, Amazon Redshift, Amazon Athena Must have active access to the output port and a configured datasource connection: a personal one, or for an agent, the agent's own connection.
The SQL should follow the datasource dialect. Try to use fully qualified table names when appropriate.
- Name
dataProductId- Type
- string
- Description
The ID of the data product
- Name
outputPortId- Type
- string
- Description
The ID / name of the output port to query
- Name
purpose- Type
- string
- Description
The business purpose for executing this query. Use a high-level description, it will be used to validate purpose. If there is a data contract, the purpose must be in line with the terms specified in the data contract.
- Name
query- Type
- string
- Description
The SQL query in the data source dialect to execute. Try to use fully qualified table names when appropriate.
Data Product Management
Save Data Product dataproduct_save
EXPERIMENTAL. Save a data product YAML specification. This will create a new data product or update an existing one. The YAML must be valid Data Product Specification (DPS) or Open Data Product Standard (ODPS) format.
- Name
yaml- Type
- string
- Description
The data product YAML
Get Data Product Schema dataproduct_schema
Get the JSON Schema for data products. Returns the latest active schema - either the default schema or a custom organization-specific schema if defined.
Data products can be specified in Data Product Specification (DPS) or Open Data Product Standard (ODPS) format. Pass the optional specificationType parameter ("dps" or "odps") to choose the format; if omitted, the organization's default data product specification type is used.
This schema can be used for validating data product specifications and understanding their structure.
- Name
specificationType- Type
- string
- Description
The data product specification type: "dps" or "odps" (optional, defaults to the organization's default)
Data Contract Management
Get Data Contract datacontract_get
Get a data contract by its ID or external ID. Returns the complete data contract specification as originally defined.
The data contract can be in ODCS (Open Data Contract Standard) or DCS format.
Pass branch to read a branch of the data contract instead (see datacontract_list_branches).
- Name
dataContractId- Type
- string
- Description
The data contract ID
- Name
branch- Type
- string
- Description
Branch of the data contract to read, by name. Omit to read the data contract itself.
Save Data Contract datacontract_save
EXPERIMENTAL. Save a data contract YAML specification. This will create a new data contract or update an existing one. The YAML must be valid ODCS (Open Data Contract Standard) or DCS format.
Pass branch to propose the change on a branch of the data contract instead (create one
with datacontract_create_branch): the data contract itself stays unchanged until a person
reviews and merges the branch in the Entropy Data UI. The YAML must then be ODCS and replaces
the branch's whole document; its id stays the data contract's. Writing to a branch takes
DATACONTRACT_BRANCH_ADD or DATACONTRACT_EDIT on the data contract's owning team.
- Name
yaml- Type
- string
- Description
The data contract YAML
- Name
branch- Type
- string
- Description
Branch of the data contract to save to, by name. Omit to save the data contract itself.
Get Data Contract Schema datacontract_schema
Get the JSON Schema for Open Data Contract Standard (ODCS). Returns the latest active schema - either the default ODCS schema or a custom organization-specific schema if defined.
This schema can be used for validating data contract specifications and understanding the structure of ODCS documents.
Get Data Contract Test Results datacontract_test_results
Get test results for a data contract. Returns the most recent test run results, optionally filtered by server name. Use the count parameter to retrieve older results (up to 20). Includes check outcomes (passed, failed, warning, error) and log messages.
- Name
dataContractId- Type
- string
- Description
The data contract ID (external ID)
- Name
server- Type
- string
- Description
The server name to filter by (optional)
- Name
count- Type
- integer
- Description
Number of test results to return (1-20, default 1)
- Name
branch- Type
- string
- Description
A branch of the data contract whose results to read instead of the contract's (optional)
Run Data Contract Test datacontract_test
Run a data contract test. Executes the configured data contract test against the specified server and returns the test results including individual check outcomes. Requires that Data Contract Tests are enabled and configured for the organization.
- Name
dataContractId- Type
- string
- Description
The data contract ID (external ID)
- Name
server- Type
- string
- Description
The server name to test against (optional, required if multiple servers are configured)
- Name
branch- Type
- string
- Description
A branch of the data contract to test instead of the contract itself (optional)
List data contract branches datacontract_list_branches
List the branches of a data contract. A branch is a copy of the data contract to propose
changes on: pass its name as branch to datacontract_get, datacontract_save and
datacontract_test, and call datacontract_get_branch_changes to see what it changes. A person
reviews and merges a branch in the Entropy Data UI.
versionState is ready when the branch's version is above the data contract's, and
needsBump otherwise; suggestedVersion is the version its changes call for, and
breakingChanges the elements that make the change a major one. behindTarget is true when
the data contract changed since the branch was cut or last updated; conflicted is true when
the branch last failed to replay onto it, and conflicts says where.
- Name
dataContractId- Type
- string
- Description
The data contract ID
Create data contract branch datacontract_create_branch
Cut a branch of a data contract to propose changes on, without changing the data contract.
The branch starts as a copy of the data contract. Pass its name as branch to
datacontract_save to write the proposed document to it, to datacontract_get to read it, and to
datacontract_test to test it. datacontract_get_branch_changes shows what the branch changes.
A person then reviews and merges it in the Entropy Data UI; merging is not available over MCP.
Only an ODCS data contract can have branches. Idempotent: creating a branch that already
exists returns it. A branch name may not be main, which is what the data contract itself is
called.
Requires DATACONTRACT_BRANCH_ADD or DATACONTRACT_EDIT on the data contract's owning team.
- Name
dataContractId- Type
- string
- Description
The data contract ID to branch from
- Name
branch- Type
- string
- Description
Name of the branch, e.g.
add-customer-email
Get data contract branch changes datacontract_get_branch_changes
What a branch changes against its data contract, element by element (schema, property,
server, quality rule, ...), the way a reviewer sees it in the Entropy Data UI. Each change has
an op (add, modify, remove), an impact, and the changed fields with before and after
values. Reordering is not a change. An empty list means the branch changes nothing.
- Name
dataContractId- Type
- string
- Description
The data contract ID the branch was cut from
- Name
branch- Type
- string
- Description
Name of the branch
Get data contract branch blast radius datacontract_get_branch_blast_radius
What merging a branch would touch beyond its data contract. causes lists the branch's changes,
each with breaking and how far it carries (reach: none, providers, consumers).
impacts lists what is affected: output ports that implement the data contract, access
agreements on those ports, input ports of consuming data products, semantic concepts the
branch links or unlinks, and assets behind the changed servers and schema objects. Each impact
names the causes that reach it and the path from the data contract.
A changed status reaches the output ports without a status of their own.
A consumer is potential: which columns it reads is not known. Data products the caller may
not see are only counted (hidden_data_product_count), as are data products further
downstream (downstream_data_product_count).
- Name
dataContractId- Type
- string
- Description
The data contract ID the branch was cut from
- Name
branch- Type
- string
- Description
Name of the branch
Semantic Layer
List semantic namespaces semantics_list_namespaces
List the semantic namespaces in the organization. Each namespace is an isolated ontology
that contains concepts and relationships. Returns the slug, display name, concept count and
declared prefixes (prefix -> namespace IRI, e.g. foaf -> http://xmlns.com/foaf/0.1/) for each
namespace. Concept and relationship iri values may be written as QNames over those prefixes.
List semantic concepts semantics_list_concepts
Enumerate concepts in a semantic namespace, with optional filters for kind, group, and tag. Returns a shallow payload (externalId, name, kind, group, description) so large namespaces stay readable. Use semantics_get_concept to drill into a single concept.
- Name
namespace- Type
- string
- Description
Ontology namespace.
- Name
kind- Type
- string
- Description
Filter by kind: entity, metric, group, shared_property, property. Omit for all.
- Name
group- Type
- string
- Description
Filter by group externalId. Returns concepts that are members of this group.
- Name
tag- Type
- string
- Description
Filter by tag. Concept must carry this tag.
- Name
limit- Type
- integer
- Description
Max results. Default 200.
- Name
branch- Type
- string
- Description
Branch of the namespace to read, by name. Omit to read the namespace itself.
Search semantic concepts semantics_search_concepts
Find concepts in a semantic namespace by keyword. Matches against name, description,
externalId, synonyms, and annotation values. Use this before authoring a new concept to check whether
something similar already exists, and to find candidate extends parents or relationship
targets by topic.
- Name
namespace- Type
- string
- Description
Ontology namespace.
- Name
query- Type
- string
- Description
Search query — matched case-insensitively against name, description, externalId, synonyms, and annotation values.
- Name
kind- Type
- string
- Description
Filter by kind: entity, metric, group, shared_property, property. Omit for all.
- Name
limit- Type
- integer
- Description
Max results. Default 50.
- Name
branch- Type
- string
- Description
Branch of the namespace to read, by name. Omit to read the namespace itself.
Get semantic concept semantics_get_concept
Return the full YAML for a single semantic concept (entity, metric, group, shared_property,
or property), including its extends parents, group membership, owner, domain, ai_context,
and annotations. The returned YAML round-trips with semantics_save_concept.
- Name
namespace- Type
- string
- Description
Ontology namespace.
- Name
externalId- Type
- string
- Description
Concept externalId.
- Name
branch- Type
- string
- Description
Branch of the namespace to read, by name. Omit to read the namespace itself.
List semantic relationships semantics_list_relationships
Enumerate relationships in a semantic namespace. Filter by concept (returns edges where the
concept is either endpoint), by type (e.g. hasProperty, relatedTo), or by both.
Structural relationships (isA, memberOf) are hidden by default — they are managed via the
extends and group fields on concepts and cannot be deleted directly.
- Name
namespace- Type
- string
- Description
Ontology namespace.
- Name
concept- Type
- string
- Description
Filter by concept externalId. Returns relationships where this concept is from or to.
- Name
type- Type
- string
- Description
Filter by relationship type (e.g. hasProperty, relatedTo). Omit for all non-structural types.
- Name
includeStructural- Type
- boolean
- Description
Include isA and memberOf relationships. Default false.
- Name
limit- Type
- integer
- Description
Max results. Default 200.
- Name
branch- Type
- string
- Description
Branch of the namespace to read, by name. Omit to read the namespace itself.
Find data products for a semantic concept semantics_find_data_products_for_concept
List the data products (and data contracts) that provide data for a given semantic concept. Match is based on the semantic link defined in each resource's authoritativeDefinitions (ODCS / ODPS) pointing at the concept IRI. Accepts either an external id (e.g. "customer") in combination with a namespace, or a concept UUID.
- Name
conceptIdOrExternalId- Type
- string
- Description
Concept external id or UUID.
- Name
namespace- Type
- string
- Description
Namespace (defaults to 'main' when external id is used).
List semantic concepts for a data product semantics_concepts_for_data_product
List the semantic concepts referenced by a data product. Reads the data product's YAML specification (ODPS) and the ODCS data contracts linked from its output ports, collects every authoritativeDefinitions entry of type "semantic", then resolves each URL back to the matching semantic concept inside the organization.
- Name
dataProductExternalId- Type
- string
- Description
Data product external id.
Semantic graph NL query semantics_nl_query
Answer a natural-language question about the organization's semantic graph by generating and optionally executing a SPARQL query. The generator is schema-aware: it retrieves the most relevant concepts via embedding similarity, prepends their metadata to the prompt, and validates the generated SPARQL with Jena. One repair attempt is made if the first query fails to parse or execute.
Typical questions:
- "which data products describe the Customer entity?"
- "list all metrics classified as financial"
- "which concepts belong to the Sales group?"
- Name
question- Type
- string
- Description
The natural-language question.
- Name
executeQuery- Type
- boolean
- Description
Whether to also execute the generated query. Defaults to true.
Run SPARQL query on semantic graph semantics_sparql_query
Run a SPARQL 1.1 SELECT, ASK, CONSTRUCT, or DESCRIBE query against the organization's semantic graph.
The graph contains:
- All semantic concepts (entities, shared properties, metrics, groups) with their metadata (labels, data types, enum values, patterns, etc.)
- Relationships between concepts (hasProperty, relatedTo, isA, memberOf)
- Virtual links to data products and data contracts via ed:describes and ed:describedBy, so you can ask questions like "which data products provide data for the 'Customer' entity?".
Custom vocabulary prefix: ed: <https://entropy-data.com/ns/ed#> Standard vocabularies available: rdf, rdfs, owl, skos, dcterms, xsd. Prefixes declared on the organization's semantic namespaces (see semantics_list_namespaces) are injected as well, so an external concept IRI can be written as e.g. acme:Customer.
SPARQL UPDATE queries are not supported.
- Name
query- Type
- string
- Description
SPARQL 1.1 query string (SELECT/ASK/CONSTRUCT/DESCRIBE).
- Name
format- Type
- string
- Description
Result format: json, xml, csv, tsv, turtle. Defaults to json.
Get semantic schemas semantics_get_schema
Return the JSON schemas for semantic concepts, relationships, and ontology documents. Call this once before authoring with semantics_save_concept, semantics_save_relationship, or semantics_save_ontology so the YAML you produce conforms to the expected shape.
Pass schema=concept|relationship|ontology to fetch a single schema, or omit for all.
- Name
schema- Type
- string
- Description
Schema name: concept, relationship, ontology, or omit for all.
Save semantic concept semantics_save_concept
Create or update a single semantic concept in the given namespace. The YAML must conform to the concept schema (call semantics_get_schema once to fetch it).
The kind field selects the concept type: entity, metric, group, shared_property, or
property. Use extends for inheritance and group for group membership; isA and memberOf
relationships are managed via these fields, not via semantics_save_relationship.
extends is the complete list of the concept's parents, so send every parent it should keep:
one you leave out is removed. Send an empty list, or omit the field, to remove them all.
Adding a property to an entity is a TWO-STEP operation. Properties are first-class concepts so they can be reused across entities, not nested fields:
- Call this tool with kind=property to create the property concept (e.g.
email). - Call semantics_save_relationship with type=hasProperty, from=<entity>, to=<property> to attach it to the owning entity (e.g. from=Customer, to=email). Skipping step 2 leaves the property orphaned. Reusable cross-entity attributes use kind=shared_property instead and are linked the same way.
iri is optional and may be a full IRI or a QName such as foaf:Agent, resolved against the
namespace's declared prefixes (see semantics_list_namespaces) and the well-known vocabularies
(rdf, rdfs, owl, skos, dcterms, xsd, foaf, schema, dc, prov). An undeclared prefix fails the save.
Errors come back as a structured errors list with stable code values (schema_violation,
yaml_parse_error, etc.). Reference-resolution issues (missing extends/group target) come
back as warnings and do not fail the save.
Pass branch to write to a branch of the namespace instead (create one with
semantics_create_branch): the namespace itself stays unchanged until a person reviews and
merges the branch in the Entropy Data UI. Writing to a branch takes
SEMANTIC_NAMESPACE_BRANCH_ADD or SEMANTIC_NAMESPACE_EDIT on the namespace's owning team.
On the namespace itself, this requires SEMANTIC_NAMESPACE_EDIT on the namespace's owning team, or SEMANTIC_NAMESPACE_ADD when the namespace does not exist yet.
- Name
namespace- Type
- string
- Description
Ontology namespace.
- Name
yaml- Type
- string
- Description
Concept YAML conforming to semantic-concept-schema.json.
- Name
branch- Type
- string
- Description
Branch of the namespace to work on, by name. Omit to work on the namespace itself.
Save semantic relationship semantics_save_relationship
Create or update a single semantic relationship in the given namespace. The YAML must conform to the relationship schema (call semantics_get_schema for the shape).
Use the roles array to identify endpoints by concept name; pass type for the
relationship semantics. Common types:
- hasProperty: attach a property (kind=property or shared_property) to an entity. from=<entity name>, to=<property name>. This is the second step after creating the property via semantics_save_concept.
- relatedTo: generic association between two entities. The default when
typeis omitted. - custom: any domain-specific verb you choose (e.g. owns, fulfills, references).
A relationship is identified by its endpoints and type, so saving the same pair again with
the same
typeupdates that edge rather than creating a second one. Thenameis a label: two different pairs may share one, and renaming does not create a new relationship.
iri is optional and may be a full IRI or a QName such as foaf:knows, resolved against the
namespace's declared prefixes (see semantics_list_namespaces). An undeclared prefix fails the save.
Refuses isA and memberOf types — manage those via semantics_save_concept with
extends and group.
Pass branch to write to a branch of the namespace instead (create one with
semantics_create_branch): the namespace itself stays unchanged until a person reviews and
merges the branch in the Entropy Data UI. Writing to a branch takes
SEMANTIC_NAMESPACE_BRANCH_ADD or SEMANTIC_NAMESPACE_EDIT on the namespace's owning team.
On the namespace itself, this requires SEMANTIC_NAMESPACE_EDIT on the namespace's owning team, or SEMANTIC_NAMESPACE_ADD when the namespace does not exist yet.
- Name
namespace- Type
- string
- Description
Ontology namespace.
- Name
yaml- Type
- string
- Description
Relationship YAML conforming to semantic-relationship-schema.json.
- Name
branch- Type
- string
- Description
Branch of the namespace to work on, by name. Omit to work on the namespace itself.
Save semantic ontology (bulk, replaces namespace) semantics_save_ontology
Write a SemanticDocument YAML as the COMPLETE state of a namespace. Use this for drafting an entire namespace in one shot — e.g. when bootstrapping a domain model. The document is processed in dependency order (groups, then shared properties, then entities/metrics, then concept properties, then relationships) so cross-references inside the document resolve.
DESTRUCTIVE: this replaces, it does not merge. Any concept or relationship the namespace already holds that the document does not mention is DELETED. To change part of an existing namespace, either use semantics_save_concept / semantics_save_relationship, or read the current ontology first and send it back in full with your edits applied.
A root-level prefixes map (prefix -> namespace IRI) lets every iri in the document be a
QName such as foaf:Agent; the map is stored on the namespace and written back by the export.
An iri over a prefix that is neither declared nor well-known fails the save.
Schema violations come back in errors and abort the save. Reference-resolution issues
(missing extends/group/roles targets) come back in warnings and the save proceeds.
Pass branch to write to a branch of the namespace instead (create one with
semantics_create_branch): the namespace itself stays unchanged until a person reviews and
merges the branch in the Entropy Data UI. Writing to a branch takes
SEMANTIC_NAMESPACE_BRANCH_ADD or SEMANTIC_NAMESPACE_EDIT on the namespace's owning team.
On the namespace itself, this requires SEMANTIC_NAMESPACE_EDIT on the namespace's owning team, or SEMANTIC_NAMESPACE_ADD when the namespace does not exist yet.
- Name
namespace- Type
- string
- Description
Ontology namespace. All concepts and relationships are written under this namespace.
- Name
yaml- Type
- string
- Description
SemanticDocument YAML conforming to semantic-ontology-schema.json.
- Name
branch- Type
- string
- Description
Branch of the namespace to work on, by name. Omit to work on the namespace itself.
Delete semantic concept semantics_delete_concept
Delete a single semantic concept by externalId. By default refuses to delete a concept that is still referenced by other relationships; pass cascade=true to delete the concept and drop the referencing edges. Returns success=true with deleted=false when the concept does not exist (idempotent).
Pass branch to write to a branch of the namespace instead (create one with
semantics_create_branch): the namespace itself stays unchanged until a person reviews and
merges the branch in the Entropy Data UI. Writing to a branch takes
SEMANTIC_NAMESPACE_BRANCH_ADD or SEMANTIC_NAMESPACE_EDIT on the namespace's owning team.
On the namespace itself, this requires SEMANTIC_NAMESPACE_DELETE on the namespace's owning team.
- Name
namespace- Type
- string
- Description
Ontology namespace.
- Name
externalId- Type
- string
- Description
Concept externalId.
- Name
cascade- Type
- boolean
- Description
If true, also delete relationships that reference this concept. Default false.
- Name
branch- Type
- string
- Description
Branch of the namespace to work on, by name. Omit to work on the namespace itself.
Delete semantic relationship semantics_delete_relationship
Delete a single semantic relationship by externalId. Refuses isA and memberOf — those are
managed by re-saving the source concept with updated extends or group. Returns
success=true with deleted=false when the relationship does not exist (idempotent).
Pass branch to write to a branch of the namespace instead (create one with
semantics_create_branch): the namespace itself stays unchanged until a person reviews and
merges the branch in the Entropy Data UI. Writing to a branch takes
SEMANTIC_NAMESPACE_BRANCH_ADD or SEMANTIC_NAMESPACE_EDIT on the namespace's owning team.
On the namespace itself, this requires SEMANTIC_NAMESPACE_DELETE on the namespace's owning team.
- Name
namespace- Type
- string
- Description
Ontology namespace.
- Name
externalId- Type
- string
- Description
Relationship externalId (returned by semantics_save_relationship or semantics_list_relationships).
- Name
branch- Type
- string
- Description
Branch of the namespace to work on, by name. Omit to work on the namespace itself.
List semantic namespace branches semantics_list_branches
List the branches of a semantic namespace. A branch is a copy of the namespace to propose
changes on: pass its name as branch to the other semantics tools to read or write it, and
call semantics_get_branch_changes to see what it changes. A person reviews and merges a branch
in the Entropy Data UI.
behindTarget is true when the namespace changed since the branch was cut or last updated.
conflicted is true when the branch last failed to replay onto the namespace; conflicts says
where. A conflicted branch cannot be merged until its conflicts are resolved in the UI.
- Name
namespace- Type
- string
- Description
Ontology namespace.
Create semantic namespace branch semantics_create_branch
Cut a branch of a semantic namespace to propose changes on, without changing the namespace.
The branch starts as a copy of the namespace. Pass its name as branch to
semantics_save_concept, semantics_save_relationship, semantics_save_ontology and the delete
tools to write to it, and to the read tools to read it. semantics_get_branch_changes shows
what the branch changes. A person then reviews and merges it in the Entropy Data UI; merging
is not available over MCP.
Idempotent: creating a branch that already exists returns it. A branch name may not be main,
which is what the namespace itself is called.
Requires SEMANTIC_NAMESPACE_BRANCH_ADD or SEMANTIC_NAMESPACE_EDIT on the namespace's owning team.
- Name
namespace- Type
- string
- Description
Ontology namespace to branch from.
- Name
branch- Type
- string
- Description
Name of the branch, e.g.
review-2026-10.
Get semantic branch changes semantics_get_branch_changes
What a branch changes against its namespace, grouped by concept, the way a reviewer sees it in
the Entropy Data UI. Each change has an op (add, modify, remove), an impact, the changed
fields with before and after values, and the changes to the concept's inline properties
and its relationships. An empty list means the branch changes nothing.
- Name
namespace- Type
- string
- Description
Ontology namespace the branch was cut from.
- Name
branch- Type
- string
- Description
Name of the branch.
Get semantic branch blast radius semantics_get_branch_blast_radius
What merging a branch would touch outside its namespace. causes lists the branch's changes,
each with how far it carries (reach: none, providers, consumers). impacts lists
what is affected: the data contracts and data products that link a changed concept (effect
dangling when the concept is removed or its IRI moves, inherits when a linked property
takes a changed data type, required flag, enum, pattern or classification from it), and
through those data contracts their output ports, access agreements, input ports and assets.
Each impact names the
causes that reach it and the path to it. Everything reached through a data contract is
potential. Data products the caller may not see are only counted.
- Name
namespace- Type
- string
- Description
Ontology namespace the branch was cut from.
- Name
branch- Type
- string
- Description
Name of the branch.