ai.entityenricher/enricher

Est-ce que ai.entityenricher/enricher est sûr ?

Au dernier audit MCP Hub, le serveur MCP « ai.entityenricher/enricher » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 58 outils

• ack_database_deltas≈ 259 tokens

  Acknowledge every delta through up_to_id after successful application, releasing its lease. Acknowledgement can permanently purge delivered deltas and entity state according to registration options; never acknowledge unapplied or failed work. Returns acknowledged and purged counts. No LLM call. Apply/ack workflow: enricher://docs/database-sync.

  Paramètres, retour & exemple (2)

  Paramètres

  • up_to_id · integer · requis
    Acknowledge every delta with id <= this value.
  • database_id · string · requis
    Database sync UUID.

  Exemple d'appel

  {"name": "ack_database_deltas", "arguments": {"up_to_id": 1, "database_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• add_schema_property≈ 380 tokens

  Add a property under the root (parent_path=''), an object path or '$defs.X'. Accepts a scalar, nested object or reference to an existing $defs entity or $enums vocabulary. Requires editor; no LLM call. Omitted nullable means required at enrichment. Adding inside $defs affects every usage site. The same validation and working-copy/publication rules as update_schema_property apply. Read the container with get_schema_part first. Property format: enricher://docs/schema-reference.

  Paramètres, retour & exemple (4)

  Paramètres

  • name · string · requis
    New property name (letters, digits, underscores).
  • schema_id · string · requis
    UUID of the saved schema.
  • definition · object · requis
    {type|ref, description?, examples?, nullable?, flags?, properties?} — 'properties' nests the same shape per child for an inline object.
  • parent_path · string · optionnel
    '' = root, or an object path / '$defs.X'.

  Exemple d'appel

  {"name": "add_schema_property", "arguments": {"name": "texte", "schema_id": "texte", "definition": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• add_semantic_concept≈ 454 tokens

  Add an identity concept at zero usage, or add text as an alias using alias_of. Requires editor; resolution may incur embedding/judge cost. Probe first; if the text already resolves to an incumbent, offer that concept instead of blindly retrying. Aliases resolving to another concept are refused. embedding_model selects a new type's space only. Returns concept details and link; manage existing aliases with update_concept_alias. See enricher://docs/semantic-ids.

  Paramètres, retour & exemple (5)

  Paramètres

  • text · string · requis
    The identity text to add.
  • alias_of · ? · optionnel
    semantic_id of the concept this text is a surface form of; omit to add a standalone concept.
  • judge_floor · ? · optionnel
    Similarity at or above which a candidate is put to the identity judge. Omit to use the organization default (Settings → Organization).
  • concept_type · string · requis
    Concept type the text belongs to.
  • embedding_model · ? · optionnel
    Composite key (provider::model) to embed a NEW concept type under.

  Exemple d'appel

  {"name": "add_semantic_concept", "arguments": {"text": "texte", "concept_type": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• analyze_sample≈ 399 tokens

  Analyze sample property ambiguity and relationship identity scoping before schema generation. Requires editor; billed analysis persists a record but does not modify the sample. Returns findings with competing interpretations and suggested_names, plus identity_scoping for sites mixing an entity's own facts with facts about its parent relationship. Names are judged in their parent context, including missing units, periods or ranges. Apply only approved corrections before create_schema_from_sample. Optional: generate_sample already checks its initial sample. How to interpret findings: enricher://docs/schema-from-sample.

  Paramètres, retour & exemple (3)

  Paramètres

  • model · string · optionnel
    Model composite key. 'auto' (default) lets the server pick the org's default schema-generation model.
  • sample_json · object · requis
    The sample entity object to analyze.
  • protected_fields · ? · optionnel
    Leaf names you own (still flagged, but no rename is proposed for them).

  Exemple d'appel

  {"name": "analyze_sample", "arguments": {"sample_json": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• analyze_schema≈ 357 tokens

  Analyze a saved schema's property ambiguity and relationship identity scoping, writing annotations to the schema. Requires editor; billed. Incremental by default; force=true rechecks all sites. Returns findings, suggested descriptions, identity-scoping annotations and pending unification proposals; it does not apply suggested structural changes. Fails with ambiguity_check_disabled if the feature is off. Use update_schema_property for approved descriptions or renames; review structural changes and publish them when linked. Interpretation and modeling guidance: enricher://docs/schema-reference.

  Paramètres, retour & exemple (3)

  Paramètres

  • force · boolean · optionnel
    Re-analyze every property, not just unannotated ones.
  • model · string · optionnel
    Model composite key. 'auto' (default) lets the server pick the org's default schema-generation model.
  • schema_id · string · requis
    UUID of the saved schema.

  Exemple d'appel

  {"name": "analyze_schema", "arguments": {"schema_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• answer_job_question≈ 383 tokens

  Resume a paused job with answers to the questions returned under pause. answers maps question IDs to {option_ids: [...], text: ...}; omitted questions use defaults. Relay consequential unanswered choices to the user unless those defaults were already authorized. Resuming may continue billed model work. Returns the next pause, terminal result or running status after wait_seconds; poll get_job_status if still running. Works with generate_sample clarification in both knowledge and source modes. See enricher://docs/documents.

  Paramètres, retour & exemple (3)

  Paramètres

  • job_id · string · requis
    Paused job ID.
  • answers · ? · optionnel
    Map of question id -> {option_ids: list[str], text: str | null}. Omit to resume with the planner's defaults.
  • wait_seconds · integer · optionnel
    How long to wait for the job's next pause or completion before returning (0 = return immediately after resuming).

  Exemple d'appel

  {"name": "answer_job_question", "arguments": {"job_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• assign_sync_host≈ 293 tokens

  Assign or clear the host provisioning a database sync. Requires owner and a sync-enabled plan. host accepts a connected host ID/name; null unassigns it. Assignment may create the physical database and start synchronization automatically. Moving hosts revokes the old host's minted credential; an existing manual pairing is not evicted. Candidates come from create_database_sync or list_database_syncs. No LLM call. Managed and manual setup: enricher://docs/database-sync.

  Paramètres, retour & exemple (2)

  Paramètres

  • host · ? · optionnel
    Sync host id or name; null clears the assignment.
  • database_id · string · requis
    Database sync UUID (from list_database_syncs).

  Exemple d'appel

  {"name": "assign_sync_host", "arguments": {"database_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• cancel_job≈ 204 tokens

  Request cancellation of a pending, running or paused LLM job. In-flight model calls may finish and persist records; remaining work is skipped. Cancellation does not roll back records or database writes. Read get_job_status and list_records(job_id=...) afterward to inspect the outcome. No new LLM call is started by this tool.

  Paramètres, retour & exemple (1)

  Paramètres

  • job_id · string · requis
    Job ID to cancel.

  Exemple d'appel

  {"name": "cancel_job", "arguments": {"job_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• classify_database_model≈ 339 tokens

  Start a billed analysis proposing database keys, SQL types, indexes and relationship ownership on a linked schema. Requires editor. Registration already starts the initial pass; use this after relevant edits. Incremental scope covers new properties or changed JSON types/multilingual flags; an empty scope does not rerun unchanged fields. Returns job_id: poll get_job_status and inspect get_schema's working copy. Correct proposals with property tools, then publish_schema to ship changes. Entity-level indexes and ownership choices: enricher://docs/database-sync.

  Paramètres, retour & exemple (2)

  Paramètres

  • model · string · optionnel
    Model composite key. 'auto' (default) lets the server pick the org's default schema-generation model, falling back to the model that generated the schema.
  • schema_id · string · requis
    Saved schema UUID to classify.

  Exemple d'appel

  {"name": "classify_database_model", "arguments": {"schema_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_benchmark_scenario≈ 1221 tokens

  Create a reusable benchmark with a mandatory scoring judge. scenario_type='enrichment' needs schema_id and entity_data (the entity to enrich, as enrich_entity takes it — refused when it carries no value; never put it in description); 'sample_generation' needs sample_request; 'schema_generation' needs entity_samples (1..20 samples of one entity type). Enrichment and schema generation need a verified gold reference via set_benchmark_reference before running. Sample generation is rubric-scored and takes no reference. Requires owner and a plan with benchmarks; creating the scenario does not run the models. Returns the scenario and link. Next call run_benchmark when its reference requirements are satisfied. See enricher://docs/model-benchmark.

  Paramètres, retour & exemple (17)

  Paramètres

  • name · string · requis
  • language · string · optionnel
    sample_generation: output language for names + values.
  • strategy · string · optionnel
    Enrichment: pinned strategy (no 'auto'): single_pass | expert_domains | multi_expertise
  • languages · ? · optionnel
    Enrichment: defaults to ['en'].
  • schema_id · ? · optionnel
    UUID of the saved schema to enrich against (enrichment only, required there).
  • description · ? · optionnel
    Free-text note shown in the Benchmarks tab; no model ever reads it. The entity to enrich goes in entity_data, never here.
  • entity_data · ? · optionnel
    Enrichment (required there): the fixed entity input every model enriches — the same JSON enrich_entity takes. Read get_schema.input_contract first: identifying fields, preserve paths and keys for supplied array items. Refused when it carries no value.
  • repetitions · integer · optionnel
    Run each model N times per run; keeps mean + consistency spread.
  • scenario_type · string · optionnel
    enrichment | sample_generation | schema_generation (immutable).
  • attachment_ids · ? · optionnel
    Attachment UUIDs included in every run.
  • entity_samples · ? · optionnel
    schema_generation: the 1..20 fixed input samples (JSON objects of one entity type) every model converts to a schema. Several samples let the scoring read evidence the reference cannot state alone (nullable, types, identity).
  • sample_request · ? · optionnel
    sample_generation: the free-text sample request every model answers — the kind of entity, what the sample must contain, any budget or structural preference (same contract as generate_sample's request).
  • typical_object · ? · optionnel
    sample_generation: a specific instance to model (e.g. 'Serena Williams').
  • enable_web_search · boolean · optionnel
    sample_generation: ground values with the model's web search.
  • naming_convention · string · optionnel
    sample_generation: auto | snake_case | camelCase.
  • generate_semantic_ids · boolean · optionnel
    schema_generation: add semantic_id properties to keyed objects.
  • scoring_judge_model_key · string · requis
    LLM judge composite key used to score results (required).

  Exemple d'appel

  {"name": "create_benchmark_scenario", "arguments": {"name": "texte", "scoring_judge_model_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_database_sync≈ 1661 tokens

  Register a saved schema for relational synchronization to PostgreSQL, MySQL or SQLite. Requires owner and a sync-enabled plan. Starts a billed classification job when available; returns database ID, classification_job_id or classification_skipped, stamped_keys and registration_notices. The webhook signing secret stays outside the MCP response and can be managed in the web app. The schema is initially unpublished: wait for classification, review keys/options/notices, then publish_schema before any data can sync. pk_strategy locks once the physical model ships. Owned child arrays replace previous membership, so omitted children are deleted on re-enrichment. purge_entity_state transfers custody to replicas; relay custody_warning. A connected host may provision automatically; otherwise get_database_setup_instructions starts browser-confirmed client pairing. Modeling, publication and delivery: enricher://docs/database-sync.

  Paramètres, retour & exemple (15)

  Paramètres

  • name · string · requis
    Name of the physical database (existing on the user's server, or created by `ee-database run --create-missing`); shared by every schema linked to this database sync. Also used (snake-cased) as the conventional replica database name by the ee-database CLI.
  • dialect · string · optionnel
    SQL dialect the deltas are rendered in: postgres | mysql | sqlite.
  • on_gaps · string · optionnel
    Admission gate — what is written when an enrichment has gaps (non-nullable fields unfilled). 'reject_entity': nothing — one gap anywhere refuses the whole enrichment. 'skip_children' (default): the entity without its incomplete children — an array item is dropped, a shared 1-1 reference is detached (child not written, parent's foreign key NULL); gaps with no such child above them still reject. 'accept_partial': everything — gaps land as NULLs, and under last-write-wins a later partial run erases what an earlier one filled.
  • schema_id · string · requis
    Saved schema UUID to connect the database to.
  • pk_strategy · string · optionnel
    surrogate (default): physical surrogate IDs with unique schema keys; natural: use schema keys as physical primary keys and restrict later re-keying. Locks once the physical model ships; decide before publication. See enricher://docs/database-sync.
  • target_host · ? · optionnel
    Sync host (id or name) that should provision and sync this registration automatically (managed ee-database mode). Omitted: auto-assigned when exactly one eligible host is connected; otherwise the response's connected_hosts lists the candidates — relay the choice to the user and call assign_sync_host, or fall back to get_database_setup_instructions for browser-confirmed manual pairing.
  • key_language · ? · optionnel
    Language of multilingual identity tokens (ISO 639-1), shared by all schemas of this database. Usually defaults to schema language when needed; publication may request it after classification. Locked once chosen for the database.
  • purge_on_ack · boolean · optionnel
    Delete delivered delta copies once acknowledged.
  • index_scalars · string · optionnel
    none: identity/feed indexes; keys: add natural keys and relation access paths; filterable (default): add dates, search intent, spatial/range roles and entity query indexes; all: every scalar. Later changes queue index migrations.
  • notify_debounce_s · integer · optionnel
    Quiet period (seconds) before a delta-available notification fires: each new delta resets the timer, so a burst is announced once. Default 5 for MCP callers (agent workflows expect near-immediate reaction); the web app defaults to 30 to coalesce human-scale editing bursts.
  • propagate_not_null · ? · optionnel
    Mirror required schema fields as SQL NOT NULL. Omitted: on for strict gap policies, off for accept_partial. True with accept_partial is refused. Later tightening requires validating existing replica rows; violations can quarantine the migration.
  • purge_entity_state · boolean · optionnel
    Delete fully delivered entity state after every linked database acknowledges it. Transfers custody to replicas, makes server snapshots incomplete and limits duplicate checks. Relay custody_warning and obtain agreement before enabling. Default false.
  • purge_on_ack_delay_days · ? · optionnel
    Grace period for purge_on_ack: keep acknowledged delta copies this many days (from acknowledgement) before the hourly purge deletes them. Omit to delete them at acknowledgement. Bounded by the plan's delta retention ceiling.
  • pattern_index_localized_keys · boolean · optionnel
    Add per-language pattern-match indexes on indexed localized keys/labels (default false). Useful for prefix autocomplete; increases write/index cost. Concrete SQL depends on the selected dialect.
  • purge_entity_state_delay_days · ? · optionnel
    Grace period for purge_entity_state: a fully-delivered entity row is kept until it has gone this many days without an update, then the hourly purge deletes it. Omit to delete it as soon as every database of the schema acknowledged it.

  Exemple d'appel

  {"name": "create_database_sync", "arguments": {"name": "texte", "schema_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_schema_from_sample≈ 1044 tokens

  Generate and auto-save a schema from reviewed samples, returning schema_id, schema content and record links. Supply entity_samples (or samples_csv), sample_record_id, or both; explicit samples override stored JSON while attachment inheritance is preserved. Samples must describe one entity type in one language. Generation combines their fields and annotates relationships; it does not redesign the approved structure. Resolve consequential modeling choices and whether to generate semantic IDs before calling; semantic IDs need an organization embedding model and add cost. Requires editor; synchronous and billed. Review returned suggestions before applying edits with property tools. Sample review and canonicalizations: enricher://docs/schema-from-sample; schema format: enricher://docs/schema-reference.

  Paramètres, retour & exemple (8)

  Paramètres

  • model · string · optionnel
    Model composite key, or auto (default) for the organization task selection. Explicit keys are discovered through list_models.
  • language · ? · optionnel
    Language of schema type names/descriptions and annotations; defaults to the sample-key language. Sample property names are not translated. Separate from enrichment output languages.
  • samples_csv · ? · optionnel
    Samples as CSV text instead of entity_samples (never both): the first row is ALWAYS the header, each data row one sample. Delimiter ',', ';' or tab; headers become identifier keys ('Author Name' -> author_name); each column gets one type (integer, number, boolean or text; empty cell = null; decimal commas read in ';'/tab text). Over 20 rows, 20 are kept, covering every column. Read the result's csv_import and relay the kept rows and renamed headers.
  • attachment_ids · ? · optionnel
    UUIDs used as source context and persisted for regeneration. With sample_record_id, omit to inherit its linked attachments; pass [] to deliberately use none, or a non-empty list to override.
  • entity_samples · ? · optionnel
    1..20 reviewed instances of one entity type. Required without sample_record_id. Explicit samples override stored JSON while keeping attachment inheritance. Fields are unioned; missing/null observations become nullable. Use consistent names across samples and array items. Single-language data only; set multilingual flags after generation with update_schema_property.
  • timeout_seconds · integer · optionnel
    Wall-clock cap; returns a timeout error past this.
  • sample_record_id · ? · optionnel
    UUID of a successful sample_generation record. Its stored sample(s) are used when entity_samples is omitted, and its linked attachments are inherited when attachment_ids is omitted.
  • generate_semantic_ids · boolean · optionnel
    Add semantic IDs to eligible keyed objects. Requires an organization embedding model and adds resolution cost. Recommend for reusable identities without stable machine keys; obtain agreement before enabling unless already authorized. Defaults false. Modeling guidance: enricher://docs/schema-from-sample.

  Exemple d'appel

  {"name": "create_schema_from_sample", "arguments": {"model": "texte", "language": "texte", "samples_csv": "texte", "attachment_ids": "texte", "entity_samples": "texte", "timeout_seconds": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_attachment≈ 222 tokens

  Permanently delete an attachment in your organization, including its stored file. No LLM call. Existing records remain, but future calls or schema regeneration cannot reuse the deleted source. Delete only when that source is no longer needed; this is not a required post-enrichment step. Returns the deleted ID and filename.

  Paramètres, retour & exemple (1)

  Paramètres

  • attachment_id · string · requis
    UUID of the attachment to delete.

  Exemple d'appel

  {"name": "delete_attachment", "arguments": {"attachment_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_benchmark_scenario≈ 186 tokens

  Delete a benchmark scenario and its stored results. Requires owner and a plan with benchmarks. No LLM call; inspect the scenario before deleting it.

  Paramètres, retour & exemple (1)

  Paramètres

  • scenario_id · string · requis
    UUID of the scenario to delete.

  Exemple d'appel

  {"name": "delete_benchmark_scenario", "arguments": {"scenario_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_database_sync≈ 428 tokens

  Delete a database registration and its queued deltas, stopping its feed. Requires owner and a sync-enabled plan; no LLM call. External replica tables remain untouched. Entity state and schema database flags remain by default; delete_entity_state and clear_database_model additionally remove data/model settings from schemas left with no registration. Obtain approval for those irreversible teardown options. See enricher://docs/database-sync.

  Paramètres, retour & exemple (3)

  Paramètres

  • database_id · string · requis
    Database sync UUID (from list_database_syncs).
  • delete_entity_state · boolean · optionnel
    Also hard-delete the stored entity state of the schemas left with no database (nothing writes to it anymore). Enrichment records are untouched. Irreversible.
  • clear_database_model · boolean · optionnel
    Also clear the database model those schemas carry (database_key, db_type, index, unique_group, shared, ordered, db_name/db_name_absolute, the classification ledger and the key-language lock), returning them to plain enrichment schemas. Implies delete_entity_state. Irreversible — a later re-link re-classifies from scratch.

  Exemple d'appel

  {"name": "delete_database_sync", "arguments": {"database_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_schema≈ 178 tokens

  Soft-delete a saved schema by UUID. Requires editor; no LLM call. Restoration and permanent deletion are available in the web app, not through this tool. Returns the deletion outcome.

  Paramètres, retour & exemple (1)

  Paramètres

  • schema_id · string · requis
    UUID of the schema to delete.

  Exemple d'appel

  {"name": "delete_schema", "arguments": {"schema_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_semantic_concepts≈ 407 tokens

  Delete concepts selected by ids, concept_types or unused_only. Defaults to impact_only=true: review affected records, schemas and replicas before obtaining approval. Execution requires editor; clearing whole types requires owner. Deletion breaks convergence with IDs already stored in replicas; future resolution may mint new IDs. An unused-only deletion still removes that vocabulary. No LLM call. Returns impact counts or deletion results. See enricher://docs/semantic-ids.

  Paramètres, retour & exemple (4)

  Paramètres

  • ids · ? · optionnel
    Explicit concept semantic_ids to delete.
  • impact_only · boolean · optionnel
    True = report the blast radius only; False = delete.
  • unused_only · boolean · optionnel
    Only concepts no record references (usage 0).
  • concept_types · ? · optionnel
    Scope to these concept types; without ids and unused_only this clears the whole types (owner role).

  Exemple d'appel

  {"name": "delete_semantic_concepts", "arguments": {"ids": "texte", "impact_only": true, "unused_only": true, "concept_types": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• enrich_entity≈ 1254 tokens

  Enrich one entity against exactly one of schema_id or target_schema, returning structured output, record_id, costs and any database outcome. Read get_schema's input_contract first (published version when linked); never invent preserve values. Models may be omitted for auto selection. Generation is billed. Two or more models fuse only when all succeed: check failed_models before reporting success. A failed leg prevents automatic fusion and database admission. classification_warning returns success=false, error_code and classification; bypass only after user confirmation. Database sync defaults on: report database.status and database_warning, including partial writes or overwrites; admission is not proof of replica delivery. Recovery and fusion: enricher://docs/enrichment-and-fusion. This tool does not expose web-search activation.

  Paramètres, retour & exemple (12)

  Paramètres

  • models · ? · optionnel
    Model composite keys. Omit or pass ['auto'] for one automatically selected model; auto alone never fuses. Use list_models for explicit choices and model-count limits.
  • strategy · string · optionnel
    auto (default — server picks from the schema) | single_pass (simple schemas, 1 LLM call) | expert_domains (medium schemas with clear domains) | multi_expertise (large multi-domain schemas, parallel per-expertise calls — best quality, higher cost)
  • languages · ? · optionnel
    ISO 639-1 codes; defaults to ['en'] server-side. The first language is the primary one used for all non-multilingual string fields; multilingual fields get one value per language.
  • schema_id · ? · optionnel
    UUID of a saved schema. Mutually exclusive with target_schema.
  • entity_data · object · requis
    Entity identifiers and supplied values. Read get_schema.input_contract first: preserve paths and keys for supplied array items are required. Identifying field names are guidance; arbitrary names are accepted.
  • database_sync · boolean · optionnel
    Whether this run feeds the schema's entity layer and linked databases. Leave true for normal enrichments. Set false for the one-model recovery leg of a failed fusion run (see the recovery ladder above): the merge_records call that follows is what should write, so the intermediate single-model write is skipped. The record itself is still saved either way.
  • target_schema · ? · optionnel
    Inline JSON Schema document in the supported Entity Enricher dialect; prefer schema_id. Format: enricher://docs/schema-reference.
  • attachment_ids · ? · optionnel
    UUIDs of attachments (from upload_attachment) to provide as source material for this enrichment.
  • timeout_seconds · integer · optionnel
    Wall-clock cap. Past it the call returns `enrichment_timeout` with the job_id and the job is cancelled — a leg still in flight may finish and persist a partial record, reachable via list_records(job_id=...) and recoverable with retry_expertises. Multi-model fusion runs and reasoning models routinely need more than the default; raise it or use start_batch_enrichment (async).
  • arbitration_model · ? · optionnel
    Optional LLM model key used to resolve fusion conflicts when 2+ models are selected. Without this, conflicts are resolved by deterministic voting.
  • classification_model · ? · optionnel
    Optional pre-flight classifier model key. When set, the entity is type-checked before enrichment to catch mismatches.
  • force_after_classification_warning · boolean · optionnel
    Set to true to bypass a previous classification warning. Use only after explicit user confirmation.

  Exemple d'appel

  {"name": "enrich_entity", "arguments": {"entity_data": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• fetch_database_deltas≈ 348 tokens

  Read the next ordered window of SQL deltas and canonical payloads for a database sync. claim=false is replayable; claim=true leases the window for 120 seconds. Apply a claimed window transactionally, including schema deltas, before ack_database_deltas. limit is also bounded by the registration's page_limit. snapshot_required pauses delivery until the replica reapplies its snapshot. No LLM call. Leasing, cursors, quarantine and snapshot handling: enricher://docs/database-sync.

  Paramètres, retour & exemple (4)

  Paramètres

  • claim · boolean · optionnel
    Lease the window (requires ack).
  • limit · integer · optionnel
  • since · integer · optionnel
    Cursor: return deltas with id > since.
  • database_id · string · requis
    Database sync UUID (from list_database_syncs).

  Exemple d'appel

  {"name": "fetch_database_deltas", "arguments": {"database_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• generate_sample≈ 1194 tokens

  Generate editable sample JSON from a free-text request for schema authoring. Without attachments, use model knowledge and optional web search; with attachments, extract from the sources only (search does not relax that rule). Each sample is one instance in one language; set sample_count separately from request. Attachments force one sample. Requires editor; generation is billed. Returns a job_id and may already be paused or complete: relay pause questions through answer_job_question, otherwise poll get_job_status. Review returned samples and warnings before create_schema_from_sample; do not silently change facts or structure. For relationship modeling, multiple documents or hybrid extraction plus research, read enricher://docs/schema-from-sample and enricher://docs/documents.

  Paramètres, retour & exemple (11)

  Paramètres

  • model · string · optionnel
    Auto (default) chooses the organization task model with attachment/search capabilities. Explicit provider::model bypasses this capability matching; provider combinations or quota may still fail.
  • request · string · optionnel
    Entity type, desired fields, scope and size/depth budget. Required without attachments; optional source-mode instructions otherwise. Put the number of instances in sample_count, not in this text.
  • language · ? · optionnel
    Output language code for the generated field names AND values (e.g. 'en', 'fr'); an explicit code applies even when attachments are in another language. Omitted (default) → the generator follows the language the request is written in (its text and any typical object), else the attachment's, else English.
  • auto_answer · ? · optionnel
    Omit or false to pause for clarification; true authorizes standard interpretations and planner defaults without asking, in either mode.
  • sample_count · integer · optionnel
    Number of same-type instances (1..20), default 1. Consider 3 varied instances when designing a schema. Attachments force 1. Inspect samples_note for under-delivery or the cap.
  • wait_seconds · integer · optionnel
    How long to wait for the first pause or completion before returning (0 = return the job_id immediately).
  • attachment_ids · ? · optionnel
    UUIDs from upload_attachment. Providing any attachment switches the call into source mode: transcribe the document or describe visible photo attributes only, with an interactive planner.
  • typical_objects · ? · optionnel
    Up to sample_count concrete instances to anchor knowledge mode (e.g. ['Sanofi', 'Pfizer']), one per generated sample in order — slots beyond len(typical_objects) are named by the model's own instance roster. In source mode the attachment remains authoritative and this is ignored.
  • existing_samples · ? · optionnel
    Samples you already hold, to extend instead of starting over: the new samples reproduce the first one's exact field set and never repeat an instance already in the set; sample_count is then the number of NEW samples (set capped at 20 in total), request is optional context, and only the new samples are returned. Knowledge mode only (no attachments).
  • enable_web_search · boolean · optionnel
    Use builtin search in knowledge mode (default false). Source mode remains source-only. With an explicit unsupported model this option is ignored. Hybrid tasks: enricher://docs/documents.
  • naming_convention · string · optionnel
    auto | snake_case | camelCase

  Exemple d'appel

  {"name": "generate_sample", "arguments": {"model": "texte", "request": "texte", "language": "texte", "auto_answer": "texte", "sample_count": 1, "wait_seconds": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_benchmark_scenario≈ 261 tokens

  Read one benchmark scenario with per-model quality, cost and speed results. include_reference=true adds the reference, the fixed entity_data and the schema-generation entity_samples. Config changes can make existing results stale. No LLM call. For a ranked subset use get_benchmark_scenario_results. Read after run_benchmark completes.

  Paramètres, retour & exemple (2)

  Paramètres

  • scenario_id · string · requis
    UUID of the scenario.
  • include_reference · boolean · optionnel
    Include reference_output + entity_data (can be large).

  Exemple d'appel

  {"name": "get_benchmark_scenario", "arguments": {"scenario_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_benchmark_scenario_results≈ 592 tokens

  Filter, rank and limit a scenario's per-model benchmark results. No LLM call. overall blends quality, speed and cost using organization task weights and is null if a component is missing. Status tags are independent: success does not exclude stale or stale_score results. Missing sort metrics come last in either direction. See enricher://docs/model-benchmark for interpretation.

  Paramètres, retour & exemple (7)

  Paramètres

  • limit · ? · optionnel
    Keep only the top N after sorting (None = all).
  • status · ? · optionnel
    Keep results carrying ANY of these tags: success | failed | stale (config_hash changed since this run, re-run it) | stale_score (reference/scoring config changed since scored, rescore it) | unscored (ran fine, never scored). Empty/None = every status.
  • sort_by · string · optionnel · overall | quality | cost | speed | last_run
    Metric to sort by.
  • providers · ? · optionnel
    Keep only these provider names (empty/None = every provider).
  • model_keys · ? · optionnel
    Keep only these model composite keys (empty/None = every model).
  • sort_order · string · optionnel · asc | desc
    Sort direction.
  • scenario_id · string · requis
    UUID of the scenario.

  Exemple d'appel

  {"name": "get_benchmark_scenario_results", "arguments": {"scenario_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_database_setup_instructions≈ 293 tokens

  Return non-secret install, browser-confirmed pairing and run instructions for an ee-database sync client. Requires owner and a sync-enabled plan; no LLM call and no credential is issued or exposed to the MCP client. Run pair_command on the intended replica host: the CLI opens verification_url, the user chooses the database and confirms, and the credential travels directly to the polling CLI. Its DSN stays on that host. Use manual pairing only when managed host provisioning is not already handling the registration. Setup: enricher://docs/database-sync.

  Paramètres, retour & exemple (1)

  Paramètres

  • database_id · string · requis
    Database sync UUID (from list_database_syncs).

  Exemple d'appel

  {"name": "get_database_setup_instructions", "arguments": {"database_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_enum_candidates≈ 249 tokens

  List observed values outside each open enum's current vocabulary, with counts from recent enrichment records. No LLM call. Use the report to propose admitted members or rejected_values, or close a vocabulary only when it is exhaustive. This read does not edit the enum. An open enum allows other values; a closed one constrains output to its members. Named enums can be read with get_schema_part and changed through update_schema. See enricher://docs/schema-reference.

  Paramètres, retour & exemple (1)

  Paramètres

  • schema_id · string · requis
    UUID of the saved schema.

  Exemple d'appel

  {"name": "get_enum_candidates", "arguments": {"schema_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_job_status≈ 468 tokens

  Read a job's status, progress and compact terminal summary with persisted record IDs. Status is pending, running, paused, completed, failed or cancelled. Relay pause questions with answer_job_question. include_result=true returns full terminal details; batch summaries count entities and database outcomes. A failed job is not usable output; inspect individual records for partial recovery. Unknown IDs may be invalid, expired or lost after restart: look for persisted outputs with list_records(job_id=...), without assuming success. events_after=<seq> adds the job's event log past that cursor (per-model completions, scoring progress, pauses) — the poll equivalent of the SSE stream; pass the returned last_seq next time. No LLM call. Polling, failure and recovery guidance: enricher://docs/enrichment-and-fusion.

  Paramètres, retour & exemple (3)

  Paramètres

  • job_id · string · requis
    Job ID returned by a start tool.
  • events_after · ? · optionnel
    Event-log cursor: 0 returns the job's events from the start, a previous call's last_seq returns only the newer ones (at most 100 per call; events_has_more says when to call again). Omit to skip the log.
  • include_result · boolean · optionnel
    Include the full terminal result payload (can be large). Default returns a compact scalar summary per model.

  Exemple d'appel

  {"name": "get_job_status", "arguments": {"job_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_record≈ 252 tokens

  Read one persisted record's structured_output, entity_input_data, validation errors, expertise verdicts and metrics. failed_expertises and partial identify incomplete work even when output exists; use retry_expertises only on a record with failed domains. Fusion metadata identifies its source models and arbitration method. database_sync, when present, reports admission and per-replica delivery state. Returns record_url and the related schema link. No LLM call. Interpretation and recovery: enricher://docs/enrichment-and-fusion.

  Paramètres, retour & exemple (1)

  Paramètres

  • record_id · string · requis
    UUID of the record.

  Exemple d'appel

  {"name": "get_record", "arguments": {"record_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_schema≈ 339 tokens

  Read a saved schema with its properties, annotations and input_contract. Before enrichment, use version='published' for a database-linked schema; default 'working' is for editing. identifying_keys guide entity naming; preserve values belong to the caller and are required; each supplied array item must carry its array_item_keys. Never invent caller-owned values. The response includes version, publish_state and schema_url. A requested published contract that does not exist returns not_found. For a small edit prefer get_schema_part. No LLM call. Contract details: enricher://docs/schema-reference.

  Paramètres, retour & exemple (2)

  Paramètres

  • version · string · optionnel
    'working' (default) — the editable copy updates/edits apply to; 'published' — the contract enrichment and database sync use (only meaningful for schemas linked to a database sync).
  • schema_id · string · requis
    UUID of the saved schema.

  Exemple d'appel

  {"name": "get_schema", "arguments": {"schema_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_schema_part≈ 308 tokens

  Read only the schema fragment needed for an edit. Omit path for the root/type index; use '$defs.X' or '$enums.X' for a definition, an object path for its subtree, or a leaf path for its property card and relations. Dot-separated paths use '[]' for array items. The response identifies shared definition usage, identity participation, database flags and whether entity state or linked databases exist. Editing a $defs property affects every usage site. Reads the working copy; no LLM call. Path examples: enricher://docs/schema-reference.

  Paramètres, retour & exemple (2)

  Paramètres

  • path · ? · optionnel
    Omit for the index; else a property/object path or '$defs.X'/'$enums.X'.
  • schema_id · string · requis
    UUID of the saved schema.

  Exemple d'appel

  {"name": "get_schema_part", "arguments": {"schema_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_semantic_concept≈ 272 tokens

  Read one concept's aliases, identity source keys, linked records and nearest neighbors within its own type/model slice. Record links are capped; records_truncated signals omitted links. neighbors_limit=0 skips neighbors. Use returned alias IDs with update_concept_alias and similarities to assess a proposed merge. No LLM call. Never compare similarities across embedding spaces or concept types. See enricher://docs/semantic-ids.

  Paramètres, retour & exemple (2)

  Paramètres

  • concept_id · string · requis
    The concept's semantic_id (UUID).
  • neighbors_limit · integer · optionnel

  Exemple d'appel

  {"name": "get_semantic_concept", "arguments": {"concept_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_stats≈ 149 tokens

  Read organization-wide record totals, success rate, tokens and cost summary. No LLM call. This tool has no job filter; use list_records(job_id=...) for a particular run and benchmark tools for comparative quality/cost/speed scores.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_stats", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• import_semantic_concepts≈ 489 tokens

  Resolve 1..1000 texts against one concept type. mint=false returns exact/matched/would_mint outcomes without minting; mint=true creates misses and requires owner (reporting requires editor). Resolution can call embeddings and the identity judge even in report mode. Review would_mint rows before authorizing creation. A new type may be initialized with embedding_model; existing types cannot switch spaces through import. Returns per-text outcomes. See enricher://docs/semantic-ids.

  Paramètres, retour & exemple (5)

  Paramètres

  • mint · boolean · optionnel
    False = report only; True = create the unmatched rows (owner role).
  • texts · array · requis
    Identity texts to resolve (1..1000).
  • judge_floor · ? · optionnel
    Similarity at or above which a candidate is put to the identity judge. Omit to use the organization default (Settings → Organization).
  • concept_type · string · requis
    Concept type (slice) to resolve against.
  • embedding_model · ? · optionnel
    Composite key (provider::model) seeding a NEW concept type's slice — an import may open the type it resolves into. Refused when that type's vocabulary already lives in another model.

  Exemple d'appel

  {"name": "import_semantic_concepts", "arguments": {"texts": [], "concept_type": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_benchmark_scenarios≈ 179 tokens

  List compact benchmark scenario summaries and total. Scenarios test enrichment, sample generation or schema generation. No LLM call. Read one with get_benchmark_scenario or create one with create_benchmark_scenario. Lifecycle and reference requirements: enricher://docs/model-benchmark.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_benchmark_scenarios", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_database_syncs≈ 252 tokens

  List a saved schema's database registrations, linked schemas, options and sync hosts. Returns pending and quarantined delta counts, projection_upgrade_pending and database links. No LLM call. Pending zero alone does not prove healthy delivery: check quarantine and migration blockers. Use list_entity_states for server-side rows and get_record for per-record delivery state. PostgreSQL, MySQL and SQLite delivery is performed by the user's sync client. See enricher://docs/database-sync.

  Paramètres, retour & exemple (1)

  Paramètres

  • schema_id · string · requis
    Saved schema UUID.

  Exemple d'appel

  {"name": "list_database_syncs", "arguments": {"schema_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_entity_states≈ 394 tokens

  Browse a schema's current merged entity rows, not per-run records. Requires editor; no LLM call. Returns identities, revision, last_record_id and optionally payload, with limit/offset pagination. Rejected entities have no row; purge_entity_state may also remove delivered rows. Server-side state does not prove the external replica has applied its deltas. Use get_record and list_database_syncs for delivery and rejection diagnostics. See enricher://docs/database-sync.

  Paramètres, retour & exemple (5)

  Paramètres

  • limit · integer · optionnel
  • offset · integer · optionnel
  • schema_id · string · requis
    Saved schema UUID.
  • entity_type · ? · optionnel
    Filter to one entity type (the response lists the types present).
  • include_payload · boolean · optionnel
    Include each entity's current merged payload. Set false for a compact identity-only listing (keys, revision, last_record_id).

  Exemple d'appel

  {"name": "list_entity_states", "arguments": {"schema_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_models≈ 258 tokens

  List available model keys, nominal capabilities, languages, strategies, auto-selected defaults and organization profile_limits. Use when choosing explicit models or checking plan limits; ordinary calls may omit models or use auto without fetching this large catalogue. Auto also accounts for attachment capabilities. is_available means a usable provider key exists, not that provider quota or every combination of tools and media will work. Missing capability flags mean unsupported on this discovery surface. default_models_web_search is a search-only preview, not attachment-specific. No LLM call. Model selection and costs: enricher://docs/enrichment-and-fusion.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_models", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_records≈ 523 tokens

  List compact, paginated records in your organization, most recent first. Filter by job_id to retrieve persisted outputs of an asynchronous workflow; type, success, model and search further narrow the result. Both per-model enrichment and arbitration records may exist for one entity. Use get_record for full output and failures; use list_entity_states for current merged entity state instead of run history. No LLM call. Fetch every page when a job produces more than one page of records.

  Paramètres, retour & exemple (7)

  Paramètres

  • page · integer · optionnel
  • model · ? · optionnel
    Filter by model composite key (e.g. 'anthropic::claude-sonnet-4-6').
  • job_id · ? · optionnel
    Filter to a single job (every model + expertise in one batch shares one job_id).
  • search · ? · optionnel
    Substring match against the entity's `name` field in the output.
  • success · ? · optionnel
    True = only successful records; False = only failed.
  • page_size · integer · optionnel
  • record_type · ? · optionnel
    Filter by type: enrichment | classification | arbitration | sample_generation | schema_generation | schema_edit | schema_annotation | ambiguity_analysis | db_classification | benchmark_scoring | playground

  Exemple d'appel

  {"name": "list_records", "arguments": {"page": 1, "model": "texte", "job_id": "texte", "search": "texte", "success": "texte", "page_size": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_schemas≈ 178 tokens

  List saved schemas in your organization, pinned first. Returns compact summaries with IDs, names and links; no LLM call. Use get_schema to inspect a chosen schema and its input contract, or get_schema_part for a targeted edit. For a database-linked schema, enrich against its published version; the working copy may contain unpublished changes.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_schemas", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_semantic_concepts≈ 532 tokens

  Browse organization concepts with aliases, usage counts and type/model facets. view='review' returns pairs escalated by the identity judge, not merely similar pairs. Returns a filtered page; use get_semantic_concept for details and neighbors. Similarities are comparable only within one concept_type/embedding_model slice. No LLM call. Vocabulary review and curation: enricher://docs/semantic-ids.

  Paramètres, retour & exemple (8)

  Paramètres

  • view · string · optionnel · concepts | review
    'concepts' = filtered concept page; 'review' = pairs the identity judge left for a person: escalated (unsure), found duplicated while answering another question, or separated at a similarity high enough to double-check.
  • limit · integer · optionnel
  • offset · integer · optionnel
  • search · ? · optionnel
    Substring match against concept texts.
  • sort_by · string · optionnel
    ref_count | text | concept_type | created_at
  • sort_order · string · optionnel · asc | desc
  • concept_types · ? · optionnel
    Restrict to these concept types (empty/None = every type).
  • min_ref_count · ? · optionnel
    Only concepts used by at least this many records.

  Exemple d'appel

  {"name": "list_semantic_concepts", "arguments": {"view": "concepts", "limit": 1, "offset": 1, "search": "texte", "sort_by": "texte", "sort_order": "asc"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• merge_records≈ 389 tokens

  Fuse two or more records of the same entity into a new arbitration record. Without arbitration_model use voting, median and union rules; with an arbiter, conflicts may incur LLM cost. Returns output, conflicts, fusion metadata and a new record ID. The merged result can feed linked databases and overwrite current entity values. Inspect database warnings and the actual fusion method; an arbiter failure can fall back to rules. Use this after separately recovered model runs, not to merge different entities. See enricher://docs/enrichment-and-fusion.

  Paramètres, retour & exemple (3)

  Paramètres

  • result_ids · array · requis
    UUIDs of the enrichment records to merge (minimum 2).
  • attachment_ids · ? · optionnel
    Attachments passed to the arbitration LLM (ignored for rule-based merges).
  • arbitration_model · ? · optionnel
    Model composite key for LLM arbitration (None = rule-based).

  Exemple d'appel

  {"name": "merge_records", "arguments": {"result_ids": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• merge_semantic_concepts≈ 335 tokens

  Merge a loser concept into a winner. Defaults to impact_only=true: inspect counts and affected replicas before obtaining approval to execute. impact_only=false requires owner and rewrites aliases, entity identities and referencing payloads, queuing convergence to linked replicas. No LLM call. Similarity alone does not establish identity; inspect get_semantic_concept and the judge review evidence first. Returns impact or merge results. See enricher://docs/semantic-ids.

  Paramètres, retour & exemple (3)

  Paramètres

  • loser_id · string · requis
    semantic_id of the concept folded into the winner.
  • winner_id · string · requis
    semantic_id of the concept that survives.
  • impact_only · boolean · optionnel
    True = report the merge's blast radius only; False = merge (owner role).

  Exemple d'appel

  {"name": "merge_semantic_concepts", "arguments": {"loser_id": "texte", "winner_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• migrate_semantic_embeddings≈ 468 tokens

  Inspect or migrate the organization's concept embedding space. action='status' is read-only; preview, start and cancel require owner. preview estimates cost and reports potential collisions; review them before authorizing start. target_model is required for preview/start; source_model and concept_types scope the move. Starting launches billed background re-embedding while enrichment continues, then switches the selected slices after coverage is complete. Cancel marks the transition cancelled; it does not guarantee interruption or rollback of in-flight work. Returns migration status or preview. See enricher://docs/semantic-ids.

  Paramètres, retour & exemple (4)

  Paramètres

  • action · string · requis · status | preview | start | cancel
    status | preview | start | cancel
  • source_model · ? · optionnel
    Embedding space to move; omitted = the org's current default.
  • target_model · ? · optionnel
    Composite key (provider::model) to move to. Required for preview/start.
  • concept_types · ? · optionnel
    Restrict the move to these concept types; empty = the whole space.

  Exemple d'appel

  {"name": "migrate_semantic_embeddings", "arguments": {"action": "status"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• move_schema_property≈ 371 tokens

  Move one property into the root, an object path or '$defs.X', preserving its flags and expertise. Requires editor; no LLM call. Moving into a definition changes every usage site. An identity composition naming the property is re-spelled automatically when the destination stays within the same 1-1 closure (identity_rebound reports it); the move is refused when it would take the key out of that closure or leave a semantic ID with no identity material, and on collisions or recursive containment. Read source and destination with get_schema_part first. Structural changes on database-linked schemas require publish_schema. Paths and migration guidance: enricher://docs/schema-reference.

  Paramètres, retour & exemple (3)

  Paramètres

  • path · string · requis
    Property path, e.g. 'ceremonies[].ceremony_type'.
  • schema_id · string · requis
    UUID of the saved schema.
  • new_parent_path · string · optionnel
    '' = root, or an object path / '$defs.X'.

  Exemple d'appel

  {"name": "move_schema_property", "arguments": {"path": "texte", "schema_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• nest_schema_region≈ 571 tokens

  Materialize an entity region from get_schema's x-entityMap. Ordinary flat members (e.g. product_id, product_name on an order line) move into a new object named after the region, regions hanging from it move along (nest them in turn inside the new object), pairing facts stay on the host, and the moved names shed the region's tokens (product_name → name) unless strip_prefix=false. Compact scalar occurrences (e.g. manufacturer_name or each therapeutic_classes[] item) are all converted to references to one shared $defs entity; host_path and strip_prefix do not apply to that form. If the schema already uses semantic IDs, the created object gets one when generation's gates allow (keyed, not only by exact values, not a pairing); no other object changes. host_path is '' for the root, an object path, 'path[]' for an array's items, or '$defs.X'. Defaults to dry_run=true: inspect the returned schema_content and notes, then persist with dry_run=false only after approval of the change. Requires editor; no LLM call. Database-linked structural edits still require publish_schema. Modeling consequences: enricher://docs/schema-reference.

  Paramètres, retour & exemple (5)

  Paramètres

  • dry_run · boolean · optionnel
    Report the rewrite without persisting it (the default).
  • host_path · string · optionnel
    Container holding the flat members ('' = root, object path, 'path[]', '$defs.X').
  • region_id · string · requis
    Entity region id from x-entityMap.regions (get_schema).
  • schema_id · string · requis
    UUID of the saved schema.
  • strip_prefix · boolean · optionnel
    Drop the region's name tokens from the moved field names.

  Exemple d'appel

  {"name": "nest_schema_region", "arguments": {"region_id": "texte", "schema_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• probe_semantic_concept≈ 445 tokens

  Preview identity resolution without adding a concept or increasing its usage. Requires editor; uncached resolution may call embeddings and the identity judge. Returns exact_hit, match or no_match, the matched concept and neighbors. Probe before adding; a matched incumbent may already represent the intended entity. embedding_model can select the space for a new concept type, not change an existing type's space. Inspect judge evidence as well as similarity. See enricher://docs/semantic-ids.

  Paramètres, retour & exemple (5)

  Paramètres

  • text · string · requis
    The identity text to resolve.
  • neighbors · integer · optionnel
  • judge_floor · ? · optionnel
    Similarity at or above which a candidate is put to the identity judge. Omit to use the organization default (Settings → Organization).
  • concept_type · string · requis
    Concept type (slice) to resolve against.
  • embedding_model · ? · optionnel
    Composite key (provider::model) to embed a NEW concept type under.

  Exemple d'appel

  {"name": "probe_semantic_concept", "arguments": {"text": "texte", "concept_type": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• publish_schema≈ 512 tokens

  Publish a database-linked schema's working copy as the contract used by enrichment and replicas. A newly linked schema sends nothing until first publication; unlinked drafts cannot be published. Requires editor; no LLM call. Call validate_only=true to inspect the diff, blockers, warnings and per-database migration_sql. Transform migrations require user-approved confirm_transforms=true; cross-schema conflicts remain blockers. key_language may be required if classification revealed a multilingual key. Returns publication state; queued migrations apply asynchronously on replicas. See enricher://docs/database-sync for the review and delivery workflow.

  Paramètres, retour & exemple (4)

  Paramètres

  • schema_id · string · requis
    UUID of the schema to publish.
  • key_language · ? · optionnel
    ISO 639-1 language for multilingual identity tokens. Normally adopted from the database lock. Supply when key_language_required requests a choice; review the suggested language with the user. Shared by all schemas of that database.
  • validate_only · boolean · optionnel
    Dry-run: return the diff + blockers without publishing.
  • confirm_transforms · boolean · optionnel
    Acknowledge a transform migration (re-key, type change, or a column/table rename) run against the replicas' own data. Required when the preview says requires_confirm — ALWAYS show the transforms to the user and get their explicit approval before passing true.

  Exemple d'appel

  {"name": "publish_schema", "arguments": {"schema_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• resolve_unify_proposal≈ 442 tokens

  Resolve one pending entity-type unification proposal from get_schema. action='accept' maps the proposed site onto the winning $def; field_map overrides proposed correspondences. Unmapped fields are retained as nullable; other usages of the winning definition are affected. action='dismiss' keeps the sites separate. Defaults to dry_run=true: inspect the returned schema_content and notes, then persist with dry_run=false only after approval of the change. Requires editor; no LLM call. Database-linked structural edits still require publish_schema. Modeling consequences: enricher://docs/schema-reference.

  Paramètres, retour & exemple (5)

  Paramètres

  • action · string · requis
    'accept' or 'dismiss'.
  • dry_run · boolean · optionnel
    Report the rewrite without persisting it (the default).
  • field_map · ? · optionnel
    accept only: override of the loser→winner field correspondence.
  • schema_id · string · requis
    UUID of the saved schema.
  • proposal_id · string · requis
    Proposal id from x-entityMap.proposals (get_schema).

  Exemple d'appel

  {"name": "resolve_unify_proposal", "arguments": {"action": "texte", "schema_id": "texte", "proposal_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retry_expertises≈ 596 tokens

  Retry only an existing record's failed expertise domains, then update its output and attempt the run's fusion/synchronization. Billed for retried work. Requires failed_expertises on that record (get_record); a surviving successful sibling is not retryable and returns no_failed_expertises. Supply its entity_input_data and saved_schema_id; model optionally substitutes the failed model. Returns job_id: poll get_job_status, then re-read get_record. When the failed leg left no record, use a one-model enrich_entity with database_sync=false followed by merge_records instead. Recovery decisions: enricher://docs/enrichment-and-fusion.

  Paramètres, retour & exemple (6)

  Paramètres

  • model · ? · optionnel
    Model to retry with (provider::model from list_models). Defaults to the record's own model — pass a stronger one when a domain fails repeatedly on it (retrying the same model that just failed usually fails again). Only the failed domains are re-run and re-billed; the record stays attributed to its original model.
  • languages · ? · optionnel
    ISO 639-1 codes; defaults to ['en'].
  • record_id · string · requis
    Enrichment record with failed expertises.
  • schema_id · ? · optionnel
    Saved schema UUID (get_record -> saved_schema_id). Or pass target_schema.
  • entity_data · object · requis
    The record's original entity input (get_record -> entity_input_data).
  • target_schema · ? · optionnel
    Raw schema dict when no saved schema exists.

  Exemple d'appel

  {"name": "retry_expertises", "arguments": {"record_id": "texte", "entity_data": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• revert_benchmark_reference_updates≈ 411 tokens

  Undo automatic edits a scoring pass made to a scenario's reference. Every scoring pass folds what the scored models showed the reference should be (a candidate the judge found better, a rule the samples prove, a value the reference lacked) and writes it into the reference — an edit a pass already made is only replaced by stronger evidence (samples, a wrong verdict, more agreeing models), never by one more model's better verdict; the log is reference_meta.auto_applied on get_benchmark_scenario, each entry with its inverse patch. Pass the revision ids to undo: the inverse is applied, the entry is marked reverted and its (path, attribute) is pinned so no later pass re-applies it (a manual set_benchmark_reference lifts every pin). Scores never go stale from this. Requires owner and a plan with benchmarks. No LLM call.

  Paramètres, retour & exemple (2)

  Paramètres

  • scenario_id · string · requis
    UUID of the scenario.
  • revision_ids · array · requis
    Ids of the reference_meta.auto_applied entries to undo (1..200).

  Exemple d'appel

  {"name": "revert_benchmark_reference_updates", "arguments": {"scenario_id": "texte", "revision_ids": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• run_benchmark≈ 453 tokens

  Start billed asynchronous execution and scoring of a benchmark. Requires owner, a benchmark-enabled plan and a judge; a verified reference is also required except for sample generation. Supply model_keys or providers; omitting both runs all active models with usable provider keys. Repetitions and judging increase cost. Returns job_id and total_models: poll get_job_status, then read get_benchmark_scenario_results. Re-running replaces each selected model's previous result. An organization's benchmark runs and scoring passes execute one at a time: a launch while another is in flight is queued (queue_position, status 'pending'), and a launch on a scenario whose run is still queued folds its models into that run (merged=true, job_id names the queued run). Reference setup and score interpretation: enricher://docs/model-benchmark.

  Paramètres, retour & exemple (3)

  Paramètres

  • providers · ? · optionnel
    Provider names (e.g. ['anthropic', 'mistral']) — runs every active model of those providers that has a valid key.
  • model_keys · ? · optionnel
    Explicit model composite keys. Overrides `providers`.
  • scenario_id · string · requis
    UUID of the scenario to run.

  Exemple d'appel

  {"name": "run_benchmark", "arguments": {"scenario_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• save_schema≈ 468 tokens

  Save a directly authored schema and return its ID and link. Requires editor; no LLM call or generation charge. schema_content is a JSON Schema 2020-12 document in Entity Enricher's supported dialect: title, type='object', properties, optional $defs and x-* extension sections. The server validates it and makes colliding names unique. Entity definitions, enum vocabularies and localized fields have different projection rules. Unknown keywords are dropped, not rejected: read ignored_keywords (path, keyword, hint) and applied_repairs in the result — a property flag such as semantic_id placed on a $defs entity object lands there, with the level it is read at. Use create_schema_from_sample to derive a schema from data, or update_schema for an existing schema. A minimal valid example and supported annotations are in enricher://docs/schema-reference.

  Paramètres, retour & exemple (4)

  Paramètres

  • name · string · requis
  • tags · ? · optionnel
    Optional tags.
  • is_pinned · boolean · optionnel
    Pin it to the top of listings.
  • schema_content · object · requis
    Full schema document: title, type=object, properties and optional $defs/x-* sections. See enricher://docs/schema-reference for a minimal example.

  Exemple d'appel

  {"name": "save_schema", "arguments": {"name": "texte", "schema_content": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• set_benchmark_reference≈ 473 tokens

  Save the gold reference for an enrichment or schema-generation benchmark. Only set reference_verified=true after checking its values against trusted evidence or obtaining human sign-off; a generated answer alone is not verification. Schema-generation references must be GeneratedJsonSchema objects. Sample-generation scenarios reject references because they are rubric-scored. Requires owner and a plan with benchmarks; no LLM call. A verified reference enables run_benchmark. See enricher://docs/model-benchmark.

  Paramètres, retour & exemple (5)

  Paramètres

  • source · ? · optionnel
    Provenance: generated | pasted | record (default 'pasted').
  • scenario_id · string · requis
    UUID of the scenario.
  • reference_output · object · requis
    Expected entity JSON for enrichment, or a schema document for schema_generation. Sample-generation scenarios do not accept a reference.
  • source_record_id · ? · optionnel
    Record UUID the reference was copied from (when source='record').
  • reference_verified · boolean · optionnel
    Explicit sign-off that the reference is correct (required to run).

  Exemple d'appel

  {"name": "set_benchmark_reference", "arguments": {"scenario_id": "texte", "reference_output": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• start_batch_enrichment≈ 826 tokens

  Start billed asynchronous enrichment of an entity list against exactly one of schema_id or target_schema. Returns job_id and total. No fixed entity-count cap; live prompt quotas and credits can stop remaining work. Each entity follows the enrichment/fusion pipeline; every model must succeed for its automatic fusion and database admission. A confident classification mismatch skips that entity without enrichment, never pauses the batch. Poll get_job_status, then list_records(job_id=...). Attachments apply to every entity. Unlike enrich_entity, this tool exposes neither database_sync=false nor web-search activation. Input contracts, partial results and recovery: enricher://docs/batch-enrichment.

  Paramètres, retour & exemple (9)

  Paramètres

  • models · ? · optionnel
    Model composite keys (call list_models to discover them). Optional: omit (or pass ['auto']) to let the server pick the org's default model — pinned per-task default if set, else the best blended benchmark score.
  • entities · array · requis
    Entities to enrich (each a free-form dict naming the entity — the schema's identifying fields ideally, but any field names work).
  • strategy · string · optionnel
    auto (default) | single_pass | expert_domains | multi_expertise
  • languages · ? · optionnel
    ISO 639-1 codes; defaults to ['en'].
  • schema_id · ? · optionnel
    UUID of a saved schema. Mutually exclusive with target_schema.
  • target_schema · ? · optionnel
    Inline schema document in the supported Entity Enricher dialect. Prefer schema_id to link records. See enricher://docs/schema-reference.
  • attachment_ids · ? · optionnel
    Attachment UUIDs applied as source material to every entity.
  • arbitration_model · ? · optionnel
    Optional LLM for auto-fusion conflict resolution (None = rule-based).
  • classification_model · ? · optionnel
    Optional classifier key. Confident mismatches skip that entity; softer verdicts become prompt context. Batch classification never pauses.

  Exemple d'appel

  {"name": "start_batch_enrichment", "arguments": {"entities": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• sync_records_to_database≈ 365 tokens

  Validate and inject stored or supplied enrichment output into the entity layer and linked syncs. May incur semantic-resolution cost. record_id alone reuses its output; adding structured_output creates a new derived record. Without record_id, supply structured_output and saved_schema_id. Each item uses the current published contract and admission gate. Only enrichment/arbitration records qualify; base records whose fusion is in the same request are skipped. Inspect each outcome for rejected or partial writes. Use after fixing a rejected output or an enrich_entity run with database_sync=false. See enricher://docs/enrichment-and-fusion.

  Paramètres, retour & exemple (1)

  Paramètres

  • items · array · requis
    Entities to inject. Each item: {record_id?, structured_output?, saved_schema_id?} — at least one of record_id / structured_output, and saved_schema_id required when there is no record_id.

  Exemple d'appel

  {"name": "sync_records_to_database", "arguments": {"items": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_benchmark_scenario≈ 834 tokens

  Edit a benchmark's test definition or scoring configuration. Requires owner and a plan with benchmarks; no model run. Only supplied fields change, but sample_params and schema_gen_params replace their parameter objects wholesale. The judge may be replaced, not cleared; scenario_type is immutable. Changed test definitions make previous results stale. Re-run affected models to refresh their scores. See enricher://docs/model-benchmark.

  Paramètres, retour & exemple (13)

  Paramètres

  • name · ? · optionnel
  • strategy · ? · optionnel
  • languages · ? · optionnel
  • schema_id · ? · optionnel
    New saved-schema UUID.
  • description · ? · optionnel
    Free-text note shown in the Benchmarks tab; no model ever reads it.
  • entity_data · ? · optionnel
    Enrichment: replacement fixed entity input (same contract as enrich_entity's entity_data; refused when it carries no value).
  • repetitions · ? · optionnel
  • scenario_id · string · requis
    UUID of the scenario.
  • sample_params · ? · optionnel
    sample_generation: full replacement task params object {request, typical_object, naming_convention, language, enable_web_search}.
  • entity_samples · ? · optionnel
    schema_generation: replacement input samples (1..20, whole list).
  • scoring_source · ? · optionnel
    Feed this scenario's results into the live per-model scores of the options API: 'organization' (owner+), 'global' (system admin only, fallback for orgs without their own source), or 'off' to stop using it.
  • schema_gen_params · ? · optionnel
    schema_generation: full replacement task params object {generate_semantic_ids}.
  • scoring_judge_model_key · ? · optionnel

  Exemple d'appel

  {"name": "update_benchmark_scenario", "arguments": {"scenario_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_concept_alias≈ 307 tokens

  Remove or promote a concept alias using alias IDs from get_semantic_concept. Requires editor; no LLM call. action='remove' stops that surface form resolving to this concept; removing the last alias is refused. action='set_canonical' changes its displayed form. To add an alias use add_semantic_concept(alias_of=...). Returns the outcome. See enricher://docs/semantic-ids.

  Paramètres, retour & exemple (3)

  Paramètres

  • action · string · requis · remove | set_canonical
    'remove' prunes the surface form; 'set_canonical' promotes it.
  • alias_id · string · requis
    The surface-form row's own id (UUID).
  • concept_id · string · requis
    The concept's semantic_id (UUID).

  Exemple d'appel

  {"name": "update_concept_alias", "arguments": {"action": "remove", "alias_id": "texte", "concept_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_schema≈ 615 tokens

  Edit a saved schema's metadata or replace its full schema_content without an LLM call. Requires editor. Only supplied values change. For one property, prefer update_schema_property, add_schema_property or move_schema_property. Replacements must use GeneratedJsonSchema; unknown keywords are dropped, not rejected, and reported in ignored_keywords / applied_repairs. On database-linked schemas this edits the working copy: neutral edits propagate automatically; structural edits take effect after publish_schema. Returns the updated schema and link. Contract and edit workflow: enricher://docs/schema-reference.

  Paramètres, retour & exemple (7)

  Paramètres

  • name · ? · optionnel
    New name (must be unique).
  • tags · ? · optionnel
    Replacement tag list.
  • is_pinned · ? · optionnel
    Pin or unpin.
  • schema_id · string · requis
    UUID of the schema to update.
  • key_language · ? · optionnel
    Pre-set the key language for multilingual database keys ahead of a database link (ISO 639-1). Settable only while the schema has no linked database and no entity state; locked afterwards.
  • schema_content · ? · optionnel
    Full replacement schema document, following get_schema.schema_content. See enricher://docs/schema-reference.
  • ambiguity_check_enabled · ? · optionnel
    Enable/disable the ambiguity check for this schema — the pass that flags properties whose name admits more than one meaning (gates analyze_schema and the generation post-pass).

  Exemple d'appel

  {"name": "update_schema", "arguments": {"schema_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_schema_property≈ 674 tokens

  Edit or remove one property by path without replacing the full schema. Requires editor; no LLM call. Only supplied fields change; null clears an entry in flags. Server validation rejects or normalizes invalid combinations and reports applied_repairs. Editing inside $defs affects every usage site. Removing an identity-source member is refused until its identity is recomposed. Renames preserve identity references and record migration intent. Database-linked schemas remain working-copy edits until publish_schema; inspect migration_grade. For additions or relocation use add_schema_property or move_schema_property. Paths, flags and rename rules: enricher://docs/schema-reference.

  Paramètres, retour & exemple (9)

  Paramètres

  • ref · ? · optionnel
    '#/$defs/X' or '#/$enums/X'; clears type.
  • path · string · requis
    Property path, e.g. 'ceremonies[].ceremony_type'.
  • type · ? · optionnel
    New JSON type (string/number/integer/boolean/array/object); clears $ref.
  • flags · ? · optionnel
    Flag updates (null clears): expertise, preserve, multilingual, language_discriminator, identifying, nullable, format, pattern, semantic_id, judge_floor, semantic_concept_type, semantic_embedding_model, database_key, db_type, db_type_length, index, unique_group, shared, ordered, db_name, db_name_absolute.
  • remove · boolean · optionnel
    Delete the property instead.
  • examples · ? · optionnel
  • new_name · ? · optionnel
    Rename the property.
  • schema_id · string · requis
    UUID of the saved schema.
  • description · ? · optionnel

  Exemple d'appel

  {"name": "update_schema_property", "arguments": {"path": "texte", "schema_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• upload_attachment≈ 368 tokens

  Upload base64 file bytes as reusable source material; returns id and requires_capability. Pass the ID in attachment_ids to sample/schema generation, enrichment or benchmarks. Supported format handling depends on server MIME policy: extracted text or model-readable binary. Prefer auto model selection for attachment capabilities. Uploading does not itself run an LLM. A generated sample with attachments is source-only; see enricher://docs/documents for formats, multiple-file behavior and research workflows. Retain attachments needed for later runs or regeneration.

  Paramètres, retour & exemple (3)

  Paramètres

  • filename · string · requis
    Original filename including extension (e.g. 'report.pdf').
  • media_type · ? · optionnel
    Optional MIME hint; the server still sniffs the magic bytes.
  • content_base64 · string · requis
    The file's bytes, base64-encoded (no data: prefix).

  Exemple d'appel

  {"name": "upload_attachment", "arguments": {"filename": "texte", "content_base64": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://entityenricher.ai/api/mcp/