mcp.senzing.com: topic on get_sdk_reference narrowed to a closed enum (parameters, params, parameter, signatures, signature, arguments, args, functions, function, methods, method, classes, class, api,

What changed

topic on get_sdk_reference narrowed to a closed enum (parameters, params, parameter, signatures, signature, arguments, args, functions, function, methods, method, classes, class, api, flags, response_schemas, response_schema, responses, migration, all); previously valid values may now be rejected. topic on reporting_guide narrowed to a closed enum (export, extract, reports, report, aggregate, summary, analytics, entity_views, entity, get, why, how, compare, data_mart, datamart, mart, schema, database, dashboard, visualization, visualize, chart, charts, graph, network, relationships, quality, accuracy, precision, recall, f1, audit, splits, merges, truth, evaluation, eval, er_quality, validation, evaluate, assessment); previously valid values may now be rejected. topic on sdk_guide narrowed to a closed enum (install, setup, configure, config, configuration, load, ingest, add_records, add, export, extract, dump, redo, redo_records, initialize, init, startup, search, find, lookup, get_entity, stewardship, steward, flag, flags, delete, remove, purge, information, info, stats, diagnostics, error_handling, errors, exceptions, full_pipeline, e2e, end_to_end, pipeline, full); previously valid values may now be rejected.

What to do

If your agents call mcp.senzing.com, pin the new snapshot, patch the affected call sites, and let a green contract check confirm the fix. If you don't use the changed tools, nothing is required, but the rest of the ecosystem just learned about it at the same moment you did.