OODS Foundry
Server Details
OODS Foundry is an object-oriented design system that extends the one you already have.
- Status
- Healthy
- Uptime
- 100.0% over 25 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- kneelinghorse/OODS-Foundry
- GitHub Stars
- 2
- Server Listing
- OODS Foundry
TDQS
Scored across 9 tools
Most tools target clearly distinct resources and actions, and descriptions cross-reference each other to clarify boundaries. However, artifact_certify and viz_render both draw and certify charts and explicitly return the same output, creating a genuine risk of selection confusion.
All names use lower snake_case and follow a readable domain-object or object-action pattern. Minor deviation exists between action-style names like catalog_list and noun-style names like object_registry, but the convention is still predictable.
Nine tools is well-scoped for a design-system registry, preview, data-fetch, and chart-certification server. Each tool appears to serve a distinct resource or operation without relying on excessive tool surface.
The surface covers reading components, objects, registry snapshots, screens, datasets, tool schemas, health status, and chart rendering/certification. It is largely complete for a read-and-certify service, though mutation or broader lifecycle operations are absent if those are expected.
Available Tools
9 toolsartifact_certifyCertify ChartARead-onlyIdempotentInspect
Draw and certify a chart from the input in chart, using matching data, brand and theme. Returns the same result as viz_render: hashes, warnings and the certification verdict, including accessibility equivalence, determinism, contrast and accuracy. Optional chart.output fields add SVG, the accessible table and narrative, or the normalized specification. A verdict can be conformant false; each pillar explains its result.
| Name | Required | Description | Default |
|---|---|---|---|
| chart | Yes | ||
| reproduce | No | Include the command and calls for reproducing this result. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds real value beyond that: it enumerates the returned artifacts (hashes, warnings, verdict, per-pillar explanations), warns that a verdict can be conformant false, and notes the optional output toggles. It does not mention cost, rate limits, or failure modes.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Four sentences, front-loaded with the core action, then returns, then optional outputs, then the verdict caveat. No filler sentences, though the clause listing pillars is dense and could be trimmed without loss.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description carries the return-value burden and does so: it names the returned fields (hashes, warnings, verdict, pillars) and the optional SVG/table/spec outputs. For a read-only tool with a large nested input schema, this is complete enough to call correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is only 50% and the two top-level parameters are chart and reproduce. The description adds meaning for chart.output (SVG, accessible table/narrative, normalized spec), but says nothing about the reproduce parameter, which the schema covers. Baseline 3 is appropriate since the nested schema does most of the documenting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource pair ('Draw and certify a chart') and names the certification pillars (accessibility equivalence, determinism, contrast, accuracy), which is more than a restatement of the title. It references viz_render as producing the 'same result', but does not clearly differentiate when certification is wanted over plain rendering, leaving sibling separation partly implicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit when-to-use or when-not guidance. The description says it 'Returns the same result as viz_render', which raises the question of why an agent would pick one over the other, yet never resolves it. Usage is only inferable from the word 'certify'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
catalog_listList ComponentsARead-onlyIdempotentInspect
Read components a page at a time. category, trait, context and status filter the list; status describes the HTML renderer. detail is brief by default, or full when filtering; summary includes tags, contexts, regions and traits. Brief and summary allow up to 200 entries; full clamps pageSize to 10 and reports the adjustment. totalCount, hasMore and nextPage describe pagination. object_registry reads objects instead.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based page index for pagination. | |
| trait | No | Filter components by trait (e.g., 'Editable', 'Searchable') | |
| detail | No | Defaults to brief unfiltered, full with filters. Both defaults are paged (filtered: 10 entries). summary adds tags, contexts, regions and traits; full includes evidence. Explicit detail without paging preserves the unbounded legacy request. | |
| status | No | Filter by legacy static-HTML status only: 'stable' = mapped HTML renderer; 'planned' = HTML fallback. Consult productReality.surfaces for React/Vue, generated-consumer and maturity evidence. | |
| context | No | Filter components by context (e.g., 'detail', 'list') | |
| category | No | Filter components by category (e.g., 'core', 'lifecycle', 'visual') | |
| pageSize | No | Components per page. Filtered calls without detail default to 10; nextPage gives the next call. | |
| reproduce | No | Include the command and calls for reproducing this result. | |
| includeInternal | No | Also list OODS Foundry's internal (non-business) objects in registry.objects, after the business objects. Without it they are left out and registry.hiddenInternal counts them. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the read-only/idempotent safety profile, yet the description adds real operational context beyond them: pageSize clamping to 10 for full detail with a reported adjustment, the 200-entry ceiling for brief/summary, and the warning that explicit detail without paging 'preserves the unbounded legacy request.' That last caveat is exactly the kind of consequence an agent needs before calling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Roughly six short sentences, each carrying distinct information, with the core read/pagination behavior front-loaded. The comma-heavy, note-like compression makes a couple of clauses need a second read, but nothing is padding.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 9-parameter list tool with no output schema, the description covers the essentials an agent must know: filter semantics, detail-mode defaults and limits, and return fields (totalCount, hasMore, nextPage plus what summary adds). Gaps are minor — includeInternal's registry effect and reproduce are left to the schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description still adds value by explaining cross-parameter interactions the schema states only locally: what status actually filters (legacy static-HTML renderer, not React/Vue), how detail and filtering select defaults, and which modes clamp pageSize. It omits reproduce and includeInternal, but the schema carries those adequately.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Names a specific verb and resource ('Read components a page at a time') and immediately distinguishes the tool from the sibling object_registry ('object_registry reads objects instead'). An agent can tell what this returns and how it differs from neighbors without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explains the conditions that change behavior — filtering selects full detail by default, unfiltered stays brief — and routes object queries to object_registry. It stops short of stating when this tool should not be used (e.g., single-component lookup), but the context and alternative are clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
design_previewLook Up Recorded ScreenBRead-onlyIdempotentInspect
Look up a recorded screen by object, context and framework. Returns its running screen URL, content hash, brand and theme. No new screen is generated. object_registry reads the definition behind the screen. Set reproduce true when the command and calls used to generate it are requested.
| Name | Required | Description | Default |
|---|---|---|---|
| object | Yes | An object with recorded screens at this version. | |
| context | No | The context the screen was composed for. | detail |
| framework | No | The framework of the generated app. | react |
| reproduce | No | Include the command and calls for reproducing this result. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety and idempotency profile is covered. The description adds that no new screen is generated and that object_registry reads the underlying definition, which is useful context, but it does not elaborate on caching, rate limits, or output format beyond naming returned fields.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences, front-loaded with the core action and return values, then a scoping clarification and a sibling reference. It is efficient and each sentence contributes, though it could be slightly tighter.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 100% schema coverage and annotations covering safety, the description is adequate for a read-only lookup. It names the returned fields and clarifies that no generation occurs, but lacks details on pagination, error cases, or output structure, which is acceptable given no output schema but leaves some gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and three parameters have enums, so the schema fully documents parameter meanings and allowed values. The description only adds a conditional note about the 'reproduce' flag, which is already described in the schema; no additional syntax or format details are provided, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource ('Look up a recorded screen') and clarifies scope with 'No new screen is generated', distinguishing it from any generation tool. It also names a relevant sibling (object_registry) and contrasts its role, which aids differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage by describing return values and a conditional flag ('Set reproduce true when the command and calls used to generate it are requested'), but it does not explicitly state when to use this tool versus alternatives like object_registry or other siblings. Guidance is implied rather than directive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
health_checkCheck HealthARead-onlyIdempotentInspect
Read the running service status, pinned version, registry counts, built brands, themes, token scopes and retained proof summaries. Uptime and latency are current process measurements; host paths are omitted. includeChangelog adds the DSL changelog, and sinceVersion keeps entries after that version. catalog_list and object_registry read the definitions behind the counts.
| Name | Required | Description | Default |
|---|---|---|---|
| reproduce | No | Include the command and calls for reproducing this result. | |
| sinceVersion | No | When provided with includeChangelog, only return changelog entries since this version. | |
| includeChangelog | No | When true, include DSL version changelog in the response. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavioral context: uptime and latency are current-process measurements (not historical), and host paths are deliberately omitted. Auth/rate-limit behavior is not mentioned, keeping it out of the top band.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, all load-bearing: the first enumerates the payload, the second states measurement caveats, the third covers flags and sibling routing. No filler or restatement of the title.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description carries the burden of describing the return, and it does so by enumerating the payload contents plus caveats on uptime/latency and omitted host paths. It does not describe the shape or nesting of the response, which is the only remaining gap for a tool with no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining the interaction semantics ('includeChangelog adds the DSL changelog, and sinceVersion keeps entries after that version') and clarifying that sinceVersion is only meaningful alongside includeChangelog. The 'reproduce' parameter is left undocumented in the description, but the schema handles it.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('read') and a concrete resource set (service status, pinned version, registry counts, brands, themes, token scopes, proof summaries), so an agent knows exactly what comes back. It also distinguishes itself from siblings by noting that catalog_list and object_registry read the definitions behind the counts, making the boundary with those tools explicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The closing sentence tells the agent when to route elsewhere: if it needs the definitions rather than counts, use catalog_list or object_registry. It also conditions includeChangelog/sinceVersion usage. It stops short of an explicit 'use this tool when...' statement or stating whether this should be called at the start of a session.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
object_registryRead Object RegistryARead-onlyIdempotentInspect
Read objects from the pinned registry. action list returns names, traits and field counts; domain, trait and maturity filter them, and includeInternal adds internal objects. action show requires name and returns its composed definition; context narrows view extensions. registry_snapshot provides an overview; design_preview looks up recorded screens.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Object name to look up (e.g. 'User', 'Product', 'Invoice') | |
| trait | No | Filter to objects composing a given trait (e.g. 'Priceable', 'lifecycle/Stateful') | |
| action | Yes | List objects or show one composed definition. | |
| domain | No | Filter to objects in a specific domain (e.g. 'core.identity', 'saas.billing') | |
| context | No | Optional: filter view_extensions to a single context (e.g. 'detail', 'list', 'form', 'timeline', 'card', 'inline') | |
| maturity | No | Filter by metadata maturity level | |
| reproduce | No | Include the command and calls for reproducing this result. | |
| includeInternal | No | Also list OODS Foundry's internal (non-business) objects, after the business objects. Without it they are left out and hiddenInternal counts them. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds non-annotation context: what each action returns, that filters narrow the list, and that includeInternal appends internal objects. It omits auth needs and any pagination/limit behavior, so not a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core purpose, then action semantics, then sibling routing. Dense semicolon clauses earn their place but are slightly packed for an 8-parameter tool, keeping it just short of ideal scannability.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 8 params, no output schema, and rich annotations, the description covers action behavior, filter applicability, and alternative tools adequately. It doesn't explain the reproduce parameter or return envelope, but nothing critical to correct invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: it ties domain/trait/maturity/includeInternal specifically to the list action and context specifically to show's view_extensions. That action-to-parameter binding is genuinely useful beyond the flat property list.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ('Read objects from the pinned registry') and immediately breaks the tool into its two modes (list vs show). It also distinguishes itself from siblings registry_snapshot and design_preview by naming them and giving their differing scope, so an agent can route without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives explicit when-to-use per action ('action list returns names, traits and field counts'; 'action show requires name and returns its composed definition'), names which params apply to list, and names the two alternative tools plus what they cover instead. This is close to full routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
registry_snapshotSnapshot RegistryARead-onlyIdempotentInspect
Read the registry summary: active objects and traits, loaded names, loader issues, etag and generatedAt. detail full includes definitions; names narrows them. includeInternal adds internal objects. Replies larger than 100,000 characters are refused with their size. object_registry reads one composed object; catalog_list reads components.
| Name | Required | Description | Default |
|---|---|---|---|
| names | No | Exact trait and object names; misses go in notFound. | |
| detail | No | summary (default), or full definitions, best with names. | summary |
| reproduce | No | Include the command and calls for reproducing this result. | |
| includeInternal | No | Also list OODS Foundry's internal (non-business) objects, after the business objects. Without it they are left out and registry.hiddenInternal counts them. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for the operational context they cannot carry: a hard 100,000-character response cap that refuses oversized replies and reports the size, plus loader-issue reporting including shadowed names. It also discloses what the default summary deliberately omits (schema, parameters, view extensions, semantics, tokens, metadata) and which draft fields are never snapshot outputs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core purpose, then progressively narrower conditionals and finally sibling routing; every sentence carries information with no filler. The telegraphic fragment style ("detail full includes definitions; names narrows them") is dense but occasionally clipped enough to require a second read.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description carries the full burden of describing return values, and it does: the summary field list, the loader-issue report, the etag/generatedAt pair, the size-refusal response, and the hiddenInternal count. Combined with complete parameter documentation and sibling routing, an agent has everything needed to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains that detail full returns definitions and is most useful combined with names, that names narrows the result set (with misses surfacing in notFound per the schema), and that includeInternal appends internal objects after business ones.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ("Read the registry summary") and enumerates what comes back: active objects and traits, loaded names, loader issues, etag and generatedAt. It explicitly differentiates from siblings by noting that object_registry reads one composed object and catalog_list reads components, so an agent can select it without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The closing sentence routes the agent to alternatives by describing what each sibling does (object_registry for a single composed object, catalog_list for components), which implies when not to use this tool. It also states the detail/names conditionals that select between summary and full output, though it never phrases an explicit "use X instead when..." exclusion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
structured_data_fetchFetch Structured DataARead-onlyIdempotentInspect
Read the tokens or manifest dataset. Full data is the default; detail summary returns section counts and the first page call. page reads lossless JSON Pointer entries; pageSize defaults to 10, at most 100, also bounded by size. meta.next continues and meta.full requests full data. includePayload false returns metadata; listVersions lists dates, version selects one, and ifNoneMatch returns matched true without unchanged payload. catalog_list reads components.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Dataset only: read a 1-based page of lossless JSON Pointer entries, each reply below 100,000 characters. Omit for full data. | |
| detail | No | Dataset only. summary returns section counts and the call for page 1; full (default) preserves the dataset. | |
| dataset | Yes | Registry dataset to return. | |
| version | No | Request a specific date-stamped version (e.g., '2026-02-24'). Omit for latest. Applies to dataset mode only. | |
| pageSize | No | Dataset entries per page, default 10, also bounded by serialized size. Reply meta gives next and full calls. | |
| reproduce | No | Include the command and calls for reproducing this result. | |
| ifNoneMatch | No | Return matched=true without payload when the ETag matches. | |
| listVersions | No | When true, return available version dates instead of payload. | |
| includePayload | No | When false, omit payload even if no ETag match occurs. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations cover safety (readOnly, idempotent, non-destructive, not open-world), so the bar is lower, and the description still adds real behavior: ETag/ifNoneMatch short-circuit returning matched=true without payload, page-size bounds, and continuation via meta.next. It does not clarify what a truncated page does to the rest of the dataset or whether pages are stable across calls.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loads the purpose correctly, but the body is a dense run-on chain of semicolon clauses that mixes parameter restatement, output hints, and an orphaned sibling note. Information is packed in but not organized by task, making it harder to scan than its length suggests.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 9-parameter, no-output-schema tool, the description covers the main mode interactions (full vs summary, page vs full, version vs listVersions, payload suppression) reasonably well. The gap is that meta.next/meta.full are referenced as output fields with no output schema to define them, so their shape is left implicit.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents each parameter's meaning, bounds, and defaults; the prose largely restates pageSize, detail, and page. The only added value is linking the params into a workflow (meta.next continues, meta.full requests full data), which is modest. Baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ("Read the tokens or manifest dataset") and enumerates the modes it supports. It gestures at sibling differentiation with "catalog_list reads components," but that clause is a dangling fragment that doesn't clearly frame it as the alternative for component data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives concrete when-to-use context for modes: full is default, summary for section counts, page for paginated JSON Pointer entries, includePayload false for metadata-only, listVersions for dates. However it never states when NOT to use the tool or spells out the routing rule to catalog_list beyond the terse fragment.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
tool_schemaRead Tool SchemaARead-onlyIdempotentInspect
Read a shipped tool schema by name and kind (input or output). Returns its JSON Schema, package-relative file, recorded file hash and source URL. tools/list describes this endpoint’s narrower accepted inputs; the full schema may describe operations outside the hosted tools.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | The tool's input schema or its output schema. | input |
| name | Yes | Any OODS Foundry tool at this version, local-only tools included. | |
| reproduce | No | Include the command and calls for reproducing this result. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the bar is low. The description nonetheless adds valuable behavioral context: what the return payload contains (JSON Schema, package-relative file, hash, source URL) and the caveat that the full schema may describe operations outside the hosted tools.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences: the first declares purpose and return contents, the second is a scoping caveat. No filler, front-loaded, each sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so the description rightly explains the return fields; annotations cover safety and idempotency. A minor gap is the absence of explicit routing to a sibling alternative, but for a simple three-param read tool this is otherwise complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and both 'kind' and 'name' already carry descriptions in the schema, including the enum values. The description restates the name/kind pair but adds no syntax, defaults, or format detail beyond what the schema provides. Baseline 3 is correct.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Read) and resource (shipped tool schema) with the discriminant (by name and kind) front-loaded. The mention of the 'kind' input/output split cleanly separates it from any sibling that reads other artifacts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies when to use via 'Read a shipped tool schema' and warns that tools/list describes this endpoint's narrower inputs, but never explicitly names an alternative tool or states when not to use this one. Usage is inferable, not spelled out.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
viz_renderRender ChartARead-onlyIdempotentInspect
Draw and certify a chart from inline data. Provide chartType and encodings with rows, a pattern with its own data, or an intent to recommend a tabular chart. Brand and theme apply to drawing and certification. The compact reply contains hashes, warnings and certification; output.svg adds the SVG drawing, includeA11y adds the table and narrative, and includeNormalizedSpec adds its specification. Request SVG when a displayed chart is needed. Up to 500 rows; optional outputs still share the 100,000-character reply bound. artifact_certify returns the same drawing and checks for an input in chart.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Optional stable identifier for the produced spec. | |
| geo | No | Inline geojson or topojson with topoObjectName, rows, join and valueField; optional point or flow fields. tool_schema gives the full contract. | |
| name | No | Optional human-friendly chart title. | |
| rows | No | Inline flat data rows. | |
| brand | No | Token brand for drawing and certification. | A |
| chord | No | Chord input: {nodes:[{name}],links:[{source,target,value}]}; links refer to node names; each directed pair must be unique. | |
| theme | No | Colour theme for drawing and certification. | light |
| intent | No | Structured request: goal, measures and dimensions, with optional chartFamily; uses rows instead of explicit chartType and encodings. | |
| output | No | Optional outputs; default reply has hashes and certification. | |
| sankey | No | Sankey input: {nodes:[{name}],links:[{source,target,value}]}; links refer to node names. Use chartType:"sankey". | |
| network | No | Force graph: nodes [{id,group}] and links [{source,target,value}], at most 250 nodes. | |
| opacity | No | Constant mark opacity for Cartesian charts only; omission keeps renderer defaults. | |
| pattern | No | Exact registered pattern identity; preserves source data and presentation. Cannot combine with chartType, data, intent or identity/presentation overrides. | |
| chartType | No | Chart family; Cartesian types need rows and encodings, others their named input. Omit to suggest from rows. | |
| encodings | No | Cartesian bindings: each needs field; optional type, aggregate, title, format (d3-format), currency (ISO 4217). | |
| hierarchy | No | Treemap/sunburst: {type:"nested",data:{name,value,children}} or {type:"adjacency_list",data:[{id,parentId,value}]}. See full schema. | |
| reproduce | No | Include the command and calls for reproducing this result. | |
| description | No | Optional override for the synthesized accessibility description. When omitted, a non-empty description is generated from the encodings. | |
| strictFields | No | Warn about unresolved fields and unmatched map joins (OODS-V131/V134). Default false preserves existing behavior. | |
| a11yEquivalence | No | Check Vega-Lite accessible equivalents (default true). Errors stop rendering; warnings are returned. ECharts-primary scaffolds are not checked here. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this a safe, idempotent, non-destructive, non-open-world read. The description goes beyond them by disclosing the reply shape (hashes, warnings, certification), that optional outputs add SVG/table/narrative/spec, and two hard limits (500 rows, 100,000-character reply bound), which is material context an agent cannot infer from annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is front-loaded with the core action and mode selection, then moves to output options and limits, with essentially no filler. It is dense — several clauses are packed per sentence — but each sentence carries usable information rather than restating the name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 20-parameter tool with nested objects and no output schema, the description supplies the missing reply contract, output toggles, size limits, and the artifact_certify relationship. Remaining specialty inputs (geo, chord, hierarchy, network) are deferred to the schema without description-level detail, so it is good but not exhaustive.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the structured fields already carry per-parameter meaning and the baseline is 3. The description adds cross-parameter semantics the schema does not state directly, e.g. the mutual exclusivity of input modes and the fact that brand/theme scope both drawing and certification — a real increment over the field-level text.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The opening sentence gives a specific verb pair and resource ('Draw and certify a chart from inline data'), then enumerates the three valid input shapes (chartType+encodings with rows, a registered pattern, or an intent). It even distinguishes itself from artifact_certify by noting that tool returns the same drawing but checks an input in chart.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It clearly states how to use each input mode and when to ask for SVG ('Request SVG when a displayed chart is needed'), which is genuine routing guidance. It stops short of explicit when-not conditions or a full comparison against siblings like design_preview, so it lands at clear-context rather than exhaustive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
4 tool updates
- Changed
artifact_certify51 fields changed- removed
Input schema / $defsRemoved value: -{ - "colorEncodingBinding": { - "description": "A color-channel encoding binding: like encodingBinding, plus an optional explicit `range` (hex colors) that overrides the baked OODS categorical palette on a nominal/ordinal color scale. `range` is only valid on the color channel.", - "oneOf": [ - { - "minLength": 1, - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "aggregate": { - "enum": [ - "sum", - "count", - "average", - "median", - "min", - "max", - "distinct" - ], - "type": "string" - }, - "field": { - "minLength": 1, - "type": "string" - }, - "range": { - "description": "Explicit hex colors for a nominal/ordinal color scale. Overrides the baked OODS categorical palette so an agent can supply its own scale (e.g. a 2-color presence scale). Applied in array order to the distinct series; a shorter range recycles (Vega domain[i]->range[i] mod len). Cartesian color only.", - "items": { - "pattern": "^#(?:[0-9a-fA-F]{3}){1,2}$", - "type": "string" - }, - "minItems": 2, - "type": "array" - }, - "scale": { - "enum": [ - "linear", - "temporal", - "log", - "sqrt", - "band", - "point", - "diverging" - ], - "type": "string" - }, - "sort": { - "oneOf": [ - { - "enum": [ - "none", - "ascending", - "descending" - ], - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "field": { - "type": "string" - }, - "order": { - "enum": [ - "ascending", - "descending" - ], - "type": "string" - } - }, - "required": [ - "field", - "order" - ], - "type": "object" - } - ], - "type": [ - "string", - "object" - ] - }, - "timeUnit": { - "enum": [ - "year", - "quarter", - "month", - "week", - "day", - "hour", - "minute", - "second" - ], - "type": "string" - }, - "title": { - "type": "string" - }, - "type": { - "description": "Force the Vega-Lite/ECharts field type, overriding the engine's data-aware inference. Overrides the inferred field type.", - "enum": [ - "quantitative", - "temporal", - "ordinal", - "nominal" - ], - "type": "string" - } - }, - "required": [ - "field" - ], - "type": "object" - } - ], - "type": [ - "string", - "object" - ] - }, - "encodingBinding": { - "description": "An encoding binding: either a bare field-name string, or an object with the field plus optional aggregate/scale/timeUnit/sort/title.", - "oneOf": [ - { - "minLength": 1, - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "aggregate": { - "enum": [ - "sum", - "count", - "average", - "median", - "min", - "max", - "distinct" - ], - "type": "string" - }, - "currency": { - "description": "ISO 4217 code of the amounts this channel encodes, for example EUR. The labels print its en-US symbol where the format has \"$\" (EUR €, GBP £); without a format they read \"$,f\" ($12,000). One currency per chart.", - "pattern": "^[A-Za-z]{3}$", - "type": "string" - }, - "field": { - "minLength": 1, - "type": "string" - }, - "format": { - "description": "Label format of this channel's axis (x, y) or legend: a d3-format specifier such as \"$,f\" or \",.0f\" (d3-time-format for a temporal field). \"$\" prints the currency symbol: the currency's, else $. Without a precision, labels take the precision of the tick step, so neighbouring ticks never print the same text. Carried in the normalized spec, so artifact_certify replays it.", - "maxLength": 64, - "minLength": 1, - "type": "string" - }, - "scale": { - "enum": [ - "linear", - "temporal", - "log", - "sqrt", - "band", - "point", - "diverging" - ], - "type": "string" - }, - "sort": { - "oneOf": [ - { - "enum": [ - "none", - "ascending", - "descending" - ], - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "field": { - "type": "string" - }, - "order": { - "enum": [ - "ascending", - "descending" - ], - "type": "string" - } - }, - "required": [ - "field", - "order" - ], - "type": "object" - } - ], - "type": [ - "string", - "object" - ] - }, - "timeUnit": { - "enum": [ - "year", - "quarter", - "month", - "week", - "day", - "hour", - "minute", - "second" - ], - "type": "string" - }, - "title": { - "type": "string" - }, - "type": { - "description": "Force the Vega-Lite/ECharts field type, overriding the engine's data-aware inference. Overrides the inferred field type.", - "enum": [ - "quantitative", - "temporal", - "ordinal", - "nominal" - ], - "type": "string" - } - }, - "required": [ - "field" - ], - "type": "object" - } - ], - "type": [ - "string", - "object" - ] - }, - "hierarchyNode": { - "additionalProperties": true, - "description": "A nested-hierarchy node: a name, an optional numeric value, and optional children (recursive). Extra fields are preserved for tooltips.", - "properties": { - "children": { - "items": { - "$ref": "#/$defs/hierarchyNode", - "type": "object" - }, - "type": "array" - }, - "name": { - "type": "string" - }, - "value": { - "type": "number" - } - }, - "required": [ - "name" - ], - "type": "object" - } -} - removed
Input schema / properties / chart / descriptionRemoved value: -"Render a real, data-bound visualization. Supply a registered pattern identity to preserve its source data and presentation, chartType + encodings for explicit mode, or rows for suggest or structured-intent mode. Retired patterns are not offered; structurally unsupported patterns return OODS-V167; pattern conflicts with explicit data, intent, or source identity/presentation overrides return OODS-V166. Brand, theme and output controls remain available." - changed
Input schema / properties / chart / properties / a11yEquivalence / descriptionPrevious value: -"Checks the drawn chart's accessible equivalents as it is rendered; on by default. For Vega-Lite charts, a rule marked error stops the render (status error, with one OODS-<rule id> code per rule in errors), and a rule marked warn is reported in warnings. Charts built from rows and encodings always pass. Set false only for a spec you supply that is known not to conform. ECharts-primary charts are not checked here, because their scaffold has no data yet."New value: +"Check Vega-Lite accessible equivalents (default true). Errors stop rendering; warnings are returned. ECharts-primary scaffolds are not checked here." - changed
Input schema / properties / chart / properties / chartType / descriptionPrevious value: -"Chart type. The tabular marks (bar->MarkBar, line->MarkLine, area->MarkArea, scatter->MarkPoint, heatmap->MarkRect) bind inline rows with x/y encodings. The hierarchy/flow/network/geo charts are explicit-only and return an ECharts option as the primary spec (no Vega-Lite equivalent): 'treemap' and 'sunburst' take the 'hierarchy' data branch; 'sankey' takes the 'sankey' data branch (nodes + value-weighted links); 'force_graph' takes the 'network' data branch (nodes + links); 'choropleth', 'bubble_map', and 'flow_map' take the 'geo' data branch (inline geometry + per-type encoding — flow_map draws origin→destination arcs); 'chord' takes the 'chord' data branch (sankey-shaped nodes + value-weighted links — a ring of category arcs joined by ribbons whose width is the value). Omit chartType to enter suggest mode (the recommender chooses a tabular type from the inferred field profiles)."New value: +"Chart family; Cartesian types need rows and encodings, others their named input. Omit to suggest from rows." - removed
Input schema / properties / chart / properties / chord / additionalPropertiesRemoved value: -false - changed
Input schema / properties / chart / properties / chord / descriptionPrevious value: -"Chord data for chartType 'chord' (explicit-only) — used instead of rows + x/y encodings. A native ECharts ribbon diagram: a ring of category arcs connected by weighted ribbons. Sankey-shaped — nodes plus value-weighted links; every link must carry a numeric 'value' (the ribbon width IS the flow magnitude) and reference existing node names — a link naming a node absent from 'nodes' fails loud (OODS-V147)."New value: +"Chord input: {nodes:[{name}],links:[{source,target,value}]}; links refer to node names; each directed pair must be unique." - removed
Input schema / properties / chart / properties / chord / propertiesRemoved value: -{ - "links": { - "description": "Directed, value-weighted ribbons between ring arcs (matched to arcs by name). Directed: source→target and target→source are distinct ribbons (a reciprocal pair is valid data). Each (source, target) pair should be unique — a duplicate directed link double-counts the ribbon and is flagged with a warning (OODS-V148).", - "items": { - "additionalProperties": true, - "properties": { - "source": { - "minLength": 1, - "type": "string" - }, - "target": { - "minLength": 1, - "type": "string" - }, - "value": { - "type": "number" - } - }, - "required": [ - "source", - "target", - "value" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - }, - "nodes": { - "description": "Ring arcs. Each carries a unique 'name'.", - "items": { - "additionalProperties": true, - "properties": { - "name": { - "minLength": 1, - "type": "string" - }, - "value": { - "type": "number" - } - }, - "required": [ - "name" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - } -} - removed
Input schema / properties / chart / properties / chord / requiredRemoved value: -[ - "nodes", - "links" -] - changed
Input schema / properties / chart / properties / encodings / descriptionPrevious value: -"Channel -> field bindings. Required, with at least x and y, when chartType is supplied (explicit mode)."New value: +"Cartesian bindings: each needs field; optional type, aggregate, title, format (d3-format), currency (ISO 4217)." - removed
Input schema / properties / chart / properties / encodings / properties / color / $refRemoved value: -"#/$defs/colorEncodingBinding" - added
Input schema / properties / chart / properties / encodings / properties / color / descriptionAdded value: +"Field name or binding." - added
Input schema / properties / chart / properties / encodings / properties / color / typeAdded value: +[ + "string", + "object" +] - removed
Input schema / properties / chart / properties / encodings / properties / detail / $refRemoved value: -"#/$defs/encodingBinding" - added
Input schema / properties / chart / properties / encodings / properties / detail / descriptionAdded value: +"Field name or binding." - added
Input schema / properties / chart / properties / encodings / properties / detail / typeAdded value: +[ + "string", + "object" +] - removed
Input schema / properties / chart / properties / encodings / properties / shape / $refRemoved value: -"#/$defs/encodingBinding" - added
Input schema / properties / chart / properties / encodings / properties / shape / descriptionAdded value: +"Field name or binding." - added
Input schema / properties / chart / properties / encodings / properties / shape / typeAdded value: +[ + "string", + "object" +] - removed
Input schema / properties / chart / properties / encodings / properties / size / $refRemoved value: -"#/$defs/encodingBinding" - added
Input schema / properties / chart / properties / encodings / properties / size / descriptionAdded value: +"Field name or binding." - added
Input schema / properties / chart / properties / encodings / properties / size / typeAdded value: +[ + "string", + "object" +] - removed
Input schema / properties / chart / properties / encodings / properties / x / $refRemoved value: -"#/$defs/encodingBinding" - added
Input schema / properties / chart / properties / encodings / properties / x / descriptionAdded value: +"Field name or binding." - added
Input schema / properties / chart / properties / encodings / properties / x / typeAdded value: +[ + "string", + "object" +] - removed
Input schema / properties / chart / properties / encodings / properties / y / $refRemoved value: -"#/$defs/encodingBinding" - added
Input schema / properties / chart / properties / encodings / properties / y / descriptionAdded value: +"Field name or binding." - added
Input schema / properties / chart / properties / encodings / properties / y / typeAdded value: +[ + "string", + "object" +] - removed
Input schema / properties / chart / properties / geo / additionalPropertiesRemoved value: -false - changed
Input schema / properties / chart / properties / geo / descriptionPrevious value: -"Geo data for chartType 'choropleth', 'bubble_map', or 'flow_map' (explicit-only) — used instead of rows + x/y encodings. Carries inline geometry (a GeoJSON FeatureCollection in 'geojson', or a TopoJSON Topology in 'topojson' + 'topoObjectName'), an optional 'join' that merges tabular 'rows' into features by key, and the per-type encoding: 'valueField' colours regions for choropleth; 'longitudeField'/'latitudeField' (+ optional 'sizeField'/'colorField') place points for bubble_map; 'originLongitudeField'/'originLatitudeField'/'destinationLongitudeField'/'destinationLatitudeField' (+ optional 'strengthField'/'curvature') draw origin→destination arcs for flow_map. Geometry is supplied inline — it is never fetched over the network. Note: geo specs are not self-contained (unlike treemap/sankey): the resolved FeatureCollection rides back on echartsSpec.__registration and the client re-registers the map by name before rendering. Geometry payloads can be large (a world atlas is ~100KB) — prefer a pre-simplified TopoJSON."New value: +"Inline geojson or topojson with topoObjectName, rows, join and valueField; optional point or flow fields. tool_schema gives the full contract." - removed
Input schema / properties / chart / properties / geo / propertiesRemoved value: -{ - "colorField": { - "description": "Bubble map: optional row field driving bubble colour.", - "minLength": 1, - "type": "string" - }, - "colorScale": { - "description": "Optional colour scale (defaults to a continuous linear ramp). 'ordinal' paints discrete per-category colours; 'diverging' ramps two hues about a neutral midpoint (zero).", - "enum": [ - "linear", - "quantize", - "quantile", - "threshold", - "ordinal", - "diverging" - ], - "type": "string" - }, - "curvature": { - "description": "Flow map: optional arc curveness (0 = straight, ~0.3 default). Bends each origin→destination line into an arc.", - "maximum": 1, - "minimum": 0, - "type": "number" - }, - "destinationLatitudeField": { - "description": "Flow map: the row field holding the destination latitude. Required for flow_map.", - "minLength": 1, - "type": "string" - }, - "destinationLongitudeField": { - "description": "Flow map: the row field holding the destination longitude. Required for flow_map.", - "minLength": 1, - "type": "string" - }, - "geojson": { - "additionalProperties": true, - "description": "Inline GeoJSON FeatureCollection (type:'FeatureCollection', features:[...]). Required for choropleth (the regions); optional base map for bubble_map.", - "type": "object" - }, - "join": { - "additionalProperties": false, - "description": "Choropleth join: merge each row into the feature whose 'featureProperty' equals the row's 'dataKey' value.", - "properties": { - "dataKey": { - "description": "Key in each tabular row.", - "minLength": 1, - "type": "string" - }, - "featureProperty": { - "description": "Matching property name in each feature's properties.", - "minLength": 1, - "type": "string" - } - }, - "required": [ - "dataKey", - "featureProperty" - ], - "type": "object" - }, - "latitudeField": { - "description": "Bubble map: the row field holding latitude. Required for bubble_map.", - "minLength": 1, - "type": "string" - }, - "longitudeField": { - "description": "Bubble map: the row field holding longitude. Required for bubble_map.", - "minLength": 1, - "type": "string" - }, - "originLatitudeField": { - "description": "Flow map: the row field holding the origin latitude. Required for flow_map.", - "minLength": 1, - "type": "string" - }, - "originLongitudeField": { - "description": "Flow map: the row field holding the origin longitude. Required for flow_map.", - "minLength": 1, - "type": "string" - }, - "rows": { - "description": "Tabular records: for choropleth, the values joined into features (paired with 'join'); for bubble_map, the points to plot.", - "items": { - "additionalProperties": true, - "type": "object" - }, - "maxItems": 5000, - "type": "array" - }, - "sizeField": { - "description": "Bubble map: optional row field driving bubble size.", - "minLength": 1, - "type": "string" - }, - "strengthField": { - "description": "Flow map: optional numeric row field whose magnitude drives each arc's line width (via a continuous visualMap).", - "minLength": 1, - "type": "string" - }, - "topoObjectName": { - "description": "Which TopoJSON object to extract (defaults to the sole object when there is exactly one).", - "minLength": 1, - "type": "string" - }, - "topojson": { - "additionalProperties": true, - "description": "Inline TopoJSON Topology (type:'Topology'); converted to a GeoJSON FeatureCollection. Set 'topoObjectName' when the topology holds more than one object.", - "type": "object" - }, - "valueField": { - "description": "Choropleth: the numeric field — in feature properties, or merged in via 'join' — whose value colours each region. Required for choropleth.", - "minLength": 1, - "type": "string" - } -} - changed
Input schema / properties / chart / properties / hierarchy / descriptionPrevious value: -"Hierarchy data for chartType 'treemap' or 'sunburst' (explicit-only) — used instead of rows + x/y encodings. A discriminated union on 'type': 'adjacency_list' (flat nodes linked by parentId; a node whose parent is missing becomes its own root) or 'nested' (a single root node with children)."New value: +"Treemap/sunburst: {type:\"nested\",data:{name,value,children}} or {type:\"adjacency_list\",data:[{id,parentId,value}]}. See full schema." - removed
Input schema / properties / chart / properties / hierarchy / oneOfRemoved value: -[ - { - "additionalProperties": false, - "properties": { - "data": { - "description": "Flat node list. Each node carries id, parentId (null for roots), and a numeric value.", - "items": { - "additionalProperties": true, - "properties": { - "id": { - "minLength": 1, - "type": "string" - }, - "name": { - "type": "string" - }, - "parentId": { - "type": [ - "string", - "null" - ] - }, - "value": { - "type": "number" - } - }, - "required": [ - "id", - "parentId", - "value" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - }, - "type": { - "const": "adjacency_list", - "type": "string" - } - }, - "required": [ - "type", - "data" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "data": { - "$ref": "#/$defs/hierarchyNode", - "type": "object" - }, - "type": { - "const": "nested", - "type": "string" - } - }, - "required": [ - "type", - "data" - ], - "type": "object" - } -] - removed
Input schema / properties / chart / properties / intent / additionalPropertiesRemoved value: -false - changed
Input schema / properties / chart / properties / intent / descriptionPrevious value: -"Structured (typed, not free-text) visualization intent — the deterministic half of the NL→viz hand-off. Supply it instead of chartType/encodings (mutually exclusive with chartType): the named measures/dimensions drive encoding, `goal` + the data drive the recommender's chartType pick, an optional `chartFamily` post-filters that pick. Requires `rows`."New value: +"Structured request: goal, measures and dimensions, with optional chartFamily; uses rows instead of explicit chartType and encodings." - removed
Input schema / properties / chart / properties / intent / propertiesRemoved value: -{ - "chartFamily": { - "description": "Optional preferred chart family. Post-filters the recommender ranking (not a scorer term) to this family, flagged lowConfidence when it was not the recommender's top pick. Constrained to the 5 tabular marks — the 8 explicit-only types are not recommender-rankable.", - "enum": [ - "bar", - "line", - "area", - "scatter", - "heatmap" - ], - "type": "string" - }, - "dimensions": { - "description": "Named dimension fields (the breakdowns/axes); may be empty (e.g. a two-measure scatter). Each name must exist among the data rows' fields. `type` is reserved in v0.1 (field types infer from the data).", - "items": { - "additionalProperties": false, - "properties": { - "name": { - "minLength": 1, - "type": "string" - }, - "type": { - "enum": [ - "quantitative", - "temporal", - "nominal", - "ordinal" - ], - "type": "string" - } - }, - "required": [ - "name" - ], - "type": "object" - }, - "type": "array" - }, - "goal": { - "description": "The analytical goal that steers the recommender (the live 7-value goal vocabulary).", - "enum": [ - "comparison", - "trend", - "composition", - "part-to-whole", - "relationship", - "intensity", - "distribution" - ], - "type": "string" - }, - "measures": { - "description": "Named measure fields (the metrics to plot). Each name must exist among the data rows' fields. `type` is reserved in v0.1 (field types infer from the data).", - "items": { - "additionalProperties": false, - "properties": { - "name": { - "minLength": 1, - "type": "string" - }, - "type": { - "enum": [ - "quantitative", - "temporal", - "nominal", - "ordinal" - ], - "type": "string" - } - }, - "required": [ - "name" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - } -} - removed
Input schema / properties / chart / properties / intent / requiredRemoved value: -[ - "goal", - "measures", - "dimensions" -] - removed
Input schema / properties / chart / properties / network / additionalPropertiesRemoved value: -false - changed
Input schema / properties / chart / properties / network / descriptionPrevious value: -"Network data for chartType 'force_graph' (explicit-only) — used instead of rows + x/y encodings. Nodes (each with a unique 'id'; an optional 'group' drives category colour) and directed links (optional numeric 'value'). Every link must reference existing node ids — a link naming a node absent from 'nodes' fails loud (OODS-V147)."New value: +"Force graph: nodes [{id,group}] and links [{source,target,value}], at most 250 nodes." - removed
Input schema / properties / chart / properties / network / propertiesRemoved value: -{ - "links": { - "description": "Directed edges between nodes (an empty array is allowed for an all-isolated-nodes graph). Each 'source'/'target' must match a node 'id' (a dangling ref fails loud, OODS-V147). Directed: source→target and target→source are distinct edges. Each (source, target) pair should be unique — a duplicate directed edge double-counts and is flagged with a warning (OODS-V148).", - "items": { - "additionalProperties": true, - "properties": { - "source": { - "minLength": 1, - "type": "string" - }, - "target": { - "minLength": 1, - "type": "string" - }, - "value": { - "type": "number" - } - }, - "required": [ - "source", - "target" - ], - "type": "object" - }, - "type": "array" - }, - "nodes": { - "description": "Graph nodes. Each carries a unique 'id'; optional 'group' (category) and 'value' (sizing).", - "items": { - "additionalProperties": true, - "properties": { - "group": { - "type": "string" - }, - "id": { - "minLength": 1, - "type": "string" - }, - "value": { - "type": "number" - } - }, - "required": [ - "id" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - } -} - removed
Input schema / properties / chart / properties / network / requiredRemoved value: -[ - "nodes", - "links" -] - changed
Input schema / properties / chart / properties / opacity / descriptionPrevious value: -"Optional constant mark opacity for the five Cartesian chart families. Preserved in normalized mark options and applied to both Vega-Lite and ECharts pixels. Omission preserves renderer defaults. Unsupported for hierarchy, network and geographic chart families."New value: +"Constant mark opacity for Cartesian charts only; omission keeps renderer defaults." - changed
Input schema / properties / chart / properties / output / descriptionPrevious value: -"Optional drawing and accessibility outputs; the default reply contains hashes and certification."New value: +"Optional outputs; default reply has hashes and certification." - changed
Input schema / properties / chart / properties / pattern / descriptionPrevious value: -"Exact versioned pattern source identity. Renderable patterns preserve source rows, identity, presentation and accessibility metadata. Retired identities are not offered (their reasons are in the viz taxonomy). Structurally unsupported scenes return OODS-V167. Static SVG shows the default selection state (OODS-V175). Cannot be combined with chartType, encodings, rows, intent, hierarchy, sankey, chord, network, geo, id, name, description or opacity (OODS-V166)."New value: +"Exact registered pattern identity; preserves source data and presentation. Cannot combine with chartType, data, intent or identity/presentation overrides." - changed
Input schema / properties / chart / properties / rows / descriptionPrevious value: -"Inline data rows — the primary data path. Bounded: a few hundred rows is the sweet spot. Each row is a flat object mapping field name to value."New value: +"Inline flat data rows." - added
Input schema / properties / chart / properties / rows / items / descriptionAdded value: +"rows item." - removed
Input schema / properties / chart / properties / sankey / additionalPropertiesRemoved value: -false - changed
Input schema / properties / chart / properties / sankey / descriptionPrevious value: -"Flow data for chartType 'sankey' (explicit-only) — used instead of rows + x/y encodings. Nodes plus value-weighted links; every link must carry a numeric 'value' (the link width IS the flow magnitude) and reference existing node names."New value: +"Sankey input: {nodes:[{name}],links:[{source,target,value}]}; links refer to node names. Use chartType:\"sankey\"." - removed
Input schema / properties / chart / properties / sankey / propertiesRemoved value: -{ - "links": { - "description": "Directed, value-weighted flows between nodes. Each (source, target) pair should be unique — a duplicate directed flow double-counts the link width. (Uniqueness is advisory for sankey; it is not warning-enforced.)", - "items": { - "additionalProperties": true, - "properties": { - "source": { - "minLength": 1, - "type": "string" - }, - "target": { - "minLength": 1, - "type": "string" - }, - "value": { - "type": "number" - } - }, - "required": [ - "source", - "target", - "value" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - }, - "nodes": { - "description": "Flow nodes. Each carries a unique 'name'; an optional numeric 'value' overrides the computed throughput.", - "items": { - "additionalProperties": true, - "properties": { - "name": { - "minLength": 1, - "type": "string" - }, - "value": { - "type": "number" - } - }, - "required": [ - "name" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - } -} - removed
Input schema / properties / chart / properties / sankey / requiredRemoved value: -[ - "nodes", - "links" -] - changed
Input schema / properties / chart / properties / strictFields / descriptionPrevious value: -"Strict field checks. When true, a data key that does not resolve is reported in warnings instead of producing a silently wrong chart: an encoding that names a field missing from every non-empty row (OODS-V131), or a choropleth region whose join key matches no map feature (OODS-V134, one per unmatched region). The default, false, keeps the current behavior, which drops unmatched map regions silently. Dashboard_render has its own strictFields, which turns OODS-V131 into an error panel through its onPanelError option."New value: +"Warn about unresolved fields and unmatched map joins (OODS-V131/V134). Default false preserves existing behavior." - removed
Input schema / properties / chart / titleRemoved value: -"Viz render input"
- Changed
catalog_list2 fields changed- changed
Input schema / properties / detail / descriptionPrevious value: -"Response detail level. Defaults to brief for unfiltered calls (each component's name, categories and one readiness label) and to full when filters are provided. summary adds tags, contexts, regions, traits and status; the evidence behind the readiness label is only in full."New value: +"Defaults to brief unfiltered, full with filters. Both defaults are paged (filtered: 10 entries). summary adds tags, contexts, regions and traits; full includes evidence. Explicit detail without paging preserves the unbounded legacy request." - changed
Input schema / properties / pageSize / descriptionPrevious value: -"Number of components per page."New value: +"Components per page. Filtered calls without detail default to 10; nextPage gives the next call."
- Changed
structured_data_fetch3 fields changed- added
Input schema / properties / detailAdded value: +{ + "description": "Dataset only. summary returns section counts and the call for page 1; full (default) preserves the dataset.", + "enum": [ + "summary", + "full" + ], + "type": "string" +} - added
Input schema / properties / pageAdded value: +{ + "description": "Dataset only: read a 1-based page of lossless JSON Pointer entries, each reply below 100,000 characters. Omit for full data.", + "minimum": 1, + "type": "integer" +} - added
Input schema / properties / pageSizeAdded value: +{ + "description": "Dataset entries per page, default 10, also bounded by serialized size. Reply meta gives next and full calls.", + "maximum": 100, + "minimum": 1, + "type": "integer" +}
- Changed
viz_render51 fields changed- removed
Input schema / $defsRemoved value: -{ - "colorEncodingBinding": { - "description": "A color-channel encoding binding: like encodingBinding, plus an optional explicit `range` (hex colors) that overrides the baked OODS categorical palette on a nominal/ordinal color scale. `range` is only valid on the color channel.", - "oneOf": [ - { - "minLength": 1, - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "aggregate": { - "enum": [ - "sum", - "count", - "average", - "median", - "min", - "max", - "distinct" - ], - "type": "string" - }, - "field": { - "minLength": 1, - "type": "string" - }, - "range": { - "description": "Explicit hex colors for a nominal/ordinal color scale. Overrides the baked OODS categorical palette so an agent can supply its own scale (e.g. a 2-color presence scale). Applied in array order to the distinct series; a shorter range recycles (Vega domain[i]->range[i] mod len). Cartesian color only.", - "items": { - "pattern": "^#(?:[0-9a-fA-F]{3}){1,2}$", - "type": "string" - }, - "minItems": 2, - "type": "array" - }, - "scale": { - "enum": [ - "linear", - "temporal", - "log", - "sqrt", - "band", - "point", - "diverging" - ], - "type": "string" - }, - "sort": { - "oneOf": [ - { - "enum": [ - "none", - "ascending", - "descending" - ], - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "field": { - "type": "string" - }, - "order": { - "enum": [ - "ascending", - "descending" - ], - "type": "string" - } - }, - "required": [ - "field", - "order" - ], - "type": "object" - } - ], - "type": [ - "string", - "object" - ] - }, - "timeUnit": { - "enum": [ - "year", - "quarter", - "month", - "week", - "day", - "hour", - "minute", - "second" - ], - "type": "string" - }, - "title": { - "type": "string" - }, - "type": { - "description": "Force the Vega-Lite/ECharts field type, overriding the engine's data-aware inference. Overrides the inferred field type.", - "enum": [ - "quantitative", - "temporal", - "ordinal", - "nominal" - ], - "type": "string" - } - }, - "required": [ - "field" - ], - "type": "object" - } - ], - "type": [ - "string", - "object" - ] - }, - "encodingBinding": { - "description": "An encoding binding: either a bare field-name string, or an object with the field plus optional aggregate/scale/timeUnit/sort/title.", - "oneOf": [ - { - "minLength": 1, - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "aggregate": { - "enum": [ - "sum", - "count", - "average", - "median", - "min", - "max", - "distinct" - ], - "type": "string" - }, - "currency": { - "description": "ISO 4217 code of the amounts this channel encodes, for example EUR. The labels print its en-US symbol where the format has \"$\" (EUR €, GBP £); without a format they read \"$,f\" ($12,000). One currency per chart.", - "pattern": "^[A-Za-z]{3}$", - "type": "string" - }, - "field": { - "minLength": 1, - "type": "string" - }, - "format": { - "description": "Label format of this channel's axis (x, y) or legend: a d3-format specifier such as \"$,f\" or \",.0f\" (d3-time-format for a temporal field). \"$\" prints the currency symbol: the currency's, else $. Without a precision, labels take the precision of the tick step, so neighbouring ticks never print the same text. Carried in the normalized spec, so artifact_certify replays it.", - "maxLength": 64, - "minLength": 1, - "type": "string" - }, - "scale": { - "enum": [ - "linear", - "temporal", - "log", - "sqrt", - "band", - "point", - "diverging" - ], - "type": "string" - }, - "sort": { - "oneOf": [ - { - "enum": [ - "none", - "ascending", - "descending" - ], - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "field": { - "type": "string" - }, - "order": { - "enum": [ - "ascending", - "descending" - ], - "type": "string" - } - }, - "required": [ - "field", - "order" - ], - "type": "object" - } - ], - "type": [ - "string", - "object" - ] - }, - "timeUnit": { - "enum": [ - "year", - "quarter", - "month", - "week", - "day", - "hour", - "minute", - "second" - ], - "type": "string" - }, - "title": { - "type": "string" - }, - "type": { - "description": "Force the Vega-Lite/ECharts field type, overriding the engine's data-aware inference. Overrides the inferred field type.", - "enum": [ - "quantitative", - "temporal", - "ordinal", - "nominal" - ], - "type": "string" - } - }, - "required": [ - "field" - ], - "type": "object" - } - ], - "type": [ - "string", - "object" - ] - }, - "hierarchyNode": { - "additionalProperties": true, - "description": "A nested-hierarchy node: a name, an optional numeric value, and optional children (recursive). Extra fields are preserved for tooltips.", - "properties": { - "children": { - "items": { - "$ref": "#/$defs/hierarchyNode", - "type": "object" - }, - "type": "array" - }, - "name": { - "type": "string" - }, - "value": { - "type": "number" - } - }, - "required": [ - "name" - ], - "type": "object" - } -} - removed
Input schema / descriptionRemoved value: -"Render a real, data-bound visualization. Supply a registered pattern identity to preserve its source data and presentation, chartType + encodings for explicit mode, or rows for suggest or structured-intent mode. Retired patterns are not offered; structurally unsupported patterns return OODS-V167; pattern conflicts with explicit data, intent, or source identity/presentation overrides return OODS-V166. Brand, theme and output controls remain available." - changed
Input schema / properties / a11yEquivalence / descriptionPrevious value: -"Checks the drawn chart's accessible equivalents as it is rendered; on by default. For Vega-Lite charts, a rule marked error stops the render (status error, with one OODS-<rule id> code per rule in errors), and a rule marked warn is reported in warnings. Charts built from rows and encodings always pass. Set false only for a spec you supply that is known not to conform. ECharts-primary charts are not checked here, because their scaffold has no data yet."New value: +"Check Vega-Lite accessible equivalents (default true). Errors stop rendering; warnings are returned. ECharts-primary scaffolds are not checked here." - changed
Input schema / properties / chartType / descriptionPrevious value: -"Chart type. The tabular marks (bar->MarkBar, line->MarkLine, area->MarkArea, scatter->MarkPoint, heatmap->MarkRect) bind inline rows with x/y encodings. The hierarchy/flow/network/geo charts are explicit-only and return an ECharts option as the primary spec (no Vega-Lite equivalent): 'treemap' and 'sunburst' take the 'hierarchy' data branch; 'sankey' takes the 'sankey' data branch (nodes + value-weighted links); 'force_graph' takes the 'network' data branch (nodes + links); 'choropleth', 'bubble_map', and 'flow_map' take the 'geo' data branch (inline geometry + per-type encoding — flow_map draws origin→destination arcs); 'chord' takes the 'chord' data branch (sankey-shaped nodes + value-weighted links — a ring of category arcs joined by ribbons whose width is the value). Omit chartType to enter suggest mode (the recommender chooses a tabular type from the inferred field profiles)."New value: +"Chart family; Cartesian types need rows and encodings, others their named input. Omit to suggest from rows." - removed
Input schema / properties / chord / additionalPropertiesRemoved value: -false - changed
Input schema / properties / chord / descriptionPrevious value: -"Chord data for chartType 'chord' (explicit-only) — used instead of rows + x/y encodings. A native ECharts ribbon diagram: a ring of category arcs connected by weighted ribbons. Sankey-shaped — nodes plus value-weighted links; every link must carry a numeric 'value' (the ribbon width IS the flow magnitude) and reference existing node names — a link naming a node absent from 'nodes' fails loud (OODS-V147)."New value: +"Chord input: {nodes:[{name}],links:[{source,target,value}]}; links refer to node names; each directed pair must be unique." - removed
Input schema / properties / chord / propertiesRemoved value: -{ - "links": { - "description": "Directed, value-weighted ribbons between ring arcs (matched to arcs by name). Directed: source→target and target→source are distinct ribbons (a reciprocal pair is valid data). Each (source, target) pair should be unique — a duplicate directed link double-counts the ribbon and is flagged with a warning (OODS-V148).", - "items": { - "additionalProperties": true, - "properties": { - "source": { - "minLength": 1, - "type": "string" - }, - "target": { - "minLength": 1, - "type": "string" - }, - "value": { - "type": "number" - } - }, - "required": [ - "source", - "target", - "value" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - }, - "nodes": { - "description": "Ring arcs. Each carries a unique 'name'.", - "items": { - "additionalProperties": true, - "properties": { - "name": { - "minLength": 1, - "type": "string" - }, - "value": { - "type": "number" - } - }, - "required": [ - "name" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - } -} - removed
Input schema / properties / chord / requiredRemoved value: -[ - "nodes", - "links" -] - changed
Input schema / properties / encodings / descriptionPrevious value: -"Channel -> field bindings. Required, with at least x and y, when chartType is supplied (explicit mode)."New value: +"Cartesian bindings: each needs field; optional type, aggregate, title, format (d3-format), currency (ISO 4217)." - removed
Input schema / properties / encodings / properties / color / $refRemoved value: -"#/$defs/colorEncodingBinding" - added
Input schema / properties / encodings / properties / color / descriptionAdded value: +"Field name or binding." - added
Input schema / properties / encodings / properties / color / typeAdded value: +[ + "string", + "object" +] - removed
Input schema / properties / encodings / properties / detail / $refRemoved value: -"#/$defs/encodingBinding" - added
Input schema / properties / encodings / properties / detail / descriptionAdded value: +"Field name or binding." - added
Input schema / properties / encodings / properties / detail / typeAdded value: +[ + "string", + "object" +] - removed
Input schema / properties / encodings / properties / shape / $refRemoved value: -"#/$defs/encodingBinding" - added
Input schema / properties / encodings / properties / shape / descriptionAdded value: +"Field name or binding." - added
Input schema / properties / encodings / properties / shape / typeAdded value: +[ + "string", + "object" +] - removed
Input schema / properties / encodings / properties / size / $refRemoved value: -"#/$defs/encodingBinding" - added
Input schema / properties / encodings / properties / size / descriptionAdded value: +"Field name or binding." - added
Input schema / properties / encodings / properties / size / typeAdded value: +[ + "string", + "object" +] - removed
Input schema / properties / encodings / properties / x / $refRemoved value: -"#/$defs/encodingBinding" - added
Input schema / properties / encodings / properties / x / descriptionAdded value: +"Field name or binding." - added
Input schema / properties / encodings / properties / x / typeAdded value: +[ + "string", + "object" +] - removed
Input schema / properties / encodings / properties / y / $refRemoved value: -"#/$defs/encodingBinding" - added
Input schema / properties / encodings / properties / y / descriptionAdded value: +"Field name or binding." - added
Input schema / properties / encodings / properties / y / typeAdded value: +[ + "string", + "object" +] - removed
Input schema / properties / geo / additionalPropertiesRemoved value: -false - changed
Input schema / properties / geo / descriptionPrevious value: -"Geo data for chartType 'choropleth', 'bubble_map', or 'flow_map' (explicit-only) — used instead of rows + x/y encodings. Carries inline geometry (a GeoJSON FeatureCollection in 'geojson', or a TopoJSON Topology in 'topojson' + 'topoObjectName'), an optional 'join' that merges tabular 'rows' into features by key, and the per-type encoding: 'valueField' colours regions for choropleth; 'longitudeField'/'latitudeField' (+ optional 'sizeField'/'colorField') place points for bubble_map; 'originLongitudeField'/'originLatitudeField'/'destinationLongitudeField'/'destinationLatitudeField' (+ optional 'strengthField'/'curvature') draw origin→destination arcs for flow_map. Geometry is supplied inline — it is never fetched over the network. Note: geo specs are not self-contained (unlike treemap/sankey): the resolved FeatureCollection rides back on echartsSpec.__registration and the client re-registers the map by name before rendering. Geometry payloads can be large (a world atlas is ~100KB) — prefer a pre-simplified TopoJSON."New value: +"Inline geojson or topojson with topoObjectName, rows, join and valueField; optional point or flow fields. tool_schema gives the full contract." - removed
Input schema / properties / geo / propertiesRemoved value: -{ - "colorField": { - "description": "Bubble map: optional row field driving bubble colour.", - "minLength": 1, - "type": "string" - }, - "colorScale": { - "description": "Optional colour scale (defaults to a continuous linear ramp). 'ordinal' paints discrete per-category colours; 'diverging' ramps two hues about a neutral midpoint (zero).", - "enum": [ - "linear", - "quantize", - "quantile", - "threshold", - "ordinal", - "diverging" - ], - "type": "string" - }, - "curvature": { - "description": "Flow map: optional arc curveness (0 = straight, ~0.3 default). Bends each origin→destination line into an arc.", - "maximum": 1, - "minimum": 0, - "type": "number" - }, - "destinationLatitudeField": { - "description": "Flow map: the row field holding the destination latitude. Required for flow_map.", - "minLength": 1, - "type": "string" - }, - "destinationLongitudeField": { - "description": "Flow map: the row field holding the destination longitude. Required for flow_map.", - "minLength": 1, - "type": "string" - }, - "geojson": { - "additionalProperties": true, - "description": "Inline GeoJSON FeatureCollection (type:'FeatureCollection', features:[...]). Required for choropleth (the regions); optional base map for bubble_map.", - "type": "object" - }, - "join": { - "additionalProperties": false, - "description": "Choropleth join: merge each row into the feature whose 'featureProperty' equals the row's 'dataKey' value.", - "properties": { - "dataKey": { - "description": "Key in each tabular row.", - "minLength": 1, - "type": "string" - }, - "featureProperty": { - "description": "Matching property name in each feature's properties.", - "minLength": 1, - "type": "string" - } - }, - "required": [ - "dataKey", - "featureProperty" - ], - "type": "object" - }, - "latitudeField": { - "description": "Bubble map: the row field holding latitude. Required for bubble_map.", - "minLength": 1, - "type": "string" - }, - "longitudeField": { - "description": "Bubble map: the row field holding longitude. Required for bubble_map.", - "minLength": 1, - "type": "string" - }, - "originLatitudeField": { - "description": "Flow map: the row field holding the origin latitude. Required for flow_map.", - "minLength": 1, - "type": "string" - }, - "originLongitudeField": { - "description": "Flow map: the row field holding the origin longitude. Required for flow_map.", - "minLength": 1, - "type": "string" - }, - "rows": { - "description": "Tabular records: for choropleth, the values joined into features (paired with 'join'); for bubble_map, the points to plot.", - "items": { - "additionalProperties": true, - "type": "object" - }, - "maxItems": 5000, - "type": "array" - }, - "sizeField": { - "description": "Bubble map: optional row field driving bubble size.", - "minLength": 1, - "type": "string" - }, - "strengthField": { - "description": "Flow map: optional numeric row field whose magnitude drives each arc's line width (via a continuous visualMap).", - "minLength": 1, - "type": "string" - }, - "topoObjectName": { - "description": "Which TopoJSON object to extract (defaults to the sole object when there is exactly one).", - "minLength": 1, - "type": "string" - }, - "topojson": { - "additionalProperties": true, - "description": "Inline TopoJSON Topology (type:'Topology'); converted to a GeoJSON FeatureCollection. Set 'topoObjectName' when the topology holds more than one object.", - "type": "object" - }, - "valueField": { - "description": "Choropleth: the numeric field — in feature properties, or merged in via 'join' — whose value colours each region. Required for choropleth.", - "minLength": 1, - "type": "string" - } -} - changed
Input schema / properties / hierarchy / descriptionPrevious value: -"Hierarchy data for chartType 'treemap' or 'sunburst' (explicit-only) — used instead of rows + x/y encodings. A discriminated union on 'type': 'adjacency_list' (flat nodes linked by parentId; a node whose parent is missing becomes its own root) or 'nested' (a single root node with children)."New value: +"Treemap/sunburst: {type:\"nested\",data:{name,value,children}} or {type:\"adjacency_list\",data:[{id,parentId,value}]}. See full schema." - removed
Input schema / properties / hierarchy / oneOfRemoved value: -[ - { - "additionalProperties": false, - "properties": { - "data": { - "description": "Flat node list. Each node carries id, parentId (null for roots), and a numeric value.", - "items": { - "additionalProperties": true, - "properties": { - "id": { - "minLength": 1, - "type": "string" - }, - "name": { - "type": "string" - }, - "parentId": { - "type": [ - "string", - "null" - ] - }, - "value": { - "type": "number" - } - }, - "required": [ - "id", - "parentId", - "value" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - }, - "type": { - "const": "adjacency_list", - "type": "string" - } - }, - "required": [ - "type", - "data" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "data": { - "$ref": "#/$defs/hierarchyNode", - "type": "object" - }, - "type": { - "const": "nested", - "type": "string" - } - }, - "required": [ - "type", - "data" - ], - "type": "object" - } -] - removed
Input schema / properties / intent / additionalPropertiesRemoved value: -false - changed
Input schema / properties / intent / descriptionPrevious value: -"Structured (typed, not free-text) visualization intent — the deterministic half of the NL→viz hand-off. Supply it instead of chartType/encodings (mutually exclusive with chartType): the named measures/dimensions drive encoding, `goal` + the data drive the recommender's chartType pick, an optional `chartFamily` post-filters that pick. Requires `rows`."New value: +"Structured request: goal, measures and dimensions, with optional chartFamily; uses rows instead of explicit chartType and encodings." - removed
Input schema / properties / intent / propertiesRemoved value: -{ - "chartFamily": { - "description": "Optional preferred chart family. Post-filters the recommender ranking (not a scorer term) to this family, flagged lowConfidence when it was not the recommender's top pick. Constrained to the 5 tabular marks — the 8 explicit-only types are not recommender-rankable.", - "enum": [ - "bar", - "line", - "area", - "scatter", - "heatmap" - ], - "type": "string" - }, - "dimensions": { - "description": "Named dimension fields (the breakdowns/axes); may be empty (e.g. a two-measure scatter). Each name must exist among the data rows' fields. `type` is reserved in v0.1 (field types infer from the data).", - "items": { - "additionalProperties": false, - "properties": { - "name": { - "minLength": 1, - "type": "string" - }, - "type": { - "enum": [ - "quantitative", - "temporal", - "nominal", - "ordinal" - ], - "type": "string" - } - }, - "required": [ - "name" - ], - "type": "object" - }, - "type": "array" - }, - "goal": { - "description": "The analytical goal that steers the recommender (the live 7-value goal vocabulary).", - "enum": [ - "comparison", - "trend", - "composition", - "part-to-whole", - "relationship", - "intensity", - "distribution" - ], - "type": "string" - }, - "measures": { - "description": "Named measure fields (the metrics to plot). Each name must exist among the data rows' fields. `type` is reserved in v0.1 (field types infer from the data).", - "items": { - "additionalProperties": false, - "properties": { - "name": { - "minLength": 1, - "type": "string" - }, - "type": { - "enum": [ - "quantitative", - "temporal", - "nominal", - "ordinal" - ], - "type": "string" - } - }, - "required": [ - "name" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - } -} - removed
Input schema / properties / intent / requiredRemoved value: -[ - "goal", - "measures", - "dimensions" -] - removed
Input schema / properties / network / additionalPropertiesRemoved value: -false - changed
Input schema / properties / network / descriptionPrevious value: -"Network data for chartType 'force_graph' (explicit-only) — used instead of rows + x/y encodings. Nodes (each with a unique 'id'; an optional 'group' drives category colour) and directed links (optional numeric 'value'). Every link must reference existing node ids — a link naming a node absent from 'nodes' fails loud (OODS-V147)."New value: +"Force graph: nodes [{id,group}] and links [{source,target,value}], at most 250 nodes." - removed
Input schema / properties / network / propertiesRemoved value: -{ - "links": { - "description": "Directed edges between nodes (an empty array is allowed for an all-isolated-nodes graph). Each 'source'/'target' must match a node 'id' (a dangling ref fails loud, OODS-V147). Directed: source→target and target→source are distinct edges. Each (source, target) pair should be unique — a duplicate directed edge double-counts and is flagged with a warning (OODS-V148).", - "items": { - "additionalProperties": true, - "properties": { - "source": { - "minLength": 1, - "type": "string" - }, - "target": { - "minLength": 1, - "type": "string" - }, - "value": { - "type": "number" - } - }, - "required": [ - "source", - "target" - ], - "type": "object" - }, - "type": "array" - }, - "nodes": { - "description": "Graph nodes. Each carries a unique 'id'; optional 'group' (category) and 'value' (sizing).", - "items": { - "additionalProperties": true, - "properties": { - "group": { - "type": "string" - }, - "id": { - "minLength": 1, - "type": "string" - }, - "value": { - "type": "number" - } - }, - "required": [ - "id" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - } -} - removed
Input schema / properties / network / requiredRemoved value: -[ - "nodes", - "links" -] - changed
Input schema / properties / opacity / descriptionPrevious value: -"Optional constant mark opacity for the five Cartesian chart families. Preserved in normalized mark options and applied to both Vega-Lite and ECharts pixels. Omission preserves renderer defaults. Unsupported for hierarchy, network and geographic chart families."New value: +"Constant mark opacity for Cartesian charts only; omission keeps renderer defaults." - changed
Input schema / properties / output / descriptionPrevious value: -"Optional drawing and accessibility outputs; the default reply contains hashes and certification."New value: +"Optional outputs; default reply has hashes and certification." - changed
Input schema / properties / pattern / descriptionPrevious value: -"Exact versioned pattern source identity. Renderable patterns preserve source rows, identity, presentation and accessibility metadata. Retired identities are not offered (their reasons are in the viz taxonomy). Structurally unsupported scenes return OODS-V167. Static SVG shows the default selection state (OODS-V175). Cannot be combined with chartType, encodings, rows, intent, hierarchy, sankey, chord, network, geo, id, name, description or opacity (OODS-V166)."New value: +"Exact registered pattern identity; preserves source data and presentation. Cannot combine with chartType, data, intent or identity/presentation overrides." - changed
Input schema / properties / rows / descriptionPrevious value: -"Inline data rows — the primary data path. Bounded: a few hundred rows is the sweet spot. Each row is a flat object mapping field name to value."New value: +"Inline flat data rows." - added
Input schema / properties / rows / items / descriptionAdded value: +"rows item." - removed
Input schema / properties / sankey / additionalPropertiesRemoved value: -false - changed
Input schema / properties / sankey / descriptionPrevious value: -"Flow data for chartType 'sankey' (explicit-only) — used instead of rows + x/y encodings. Nodes plus value-weighted links; every link must carry a numeric 'value' (the link width IS the flow magnitude) and reference existing node names."New value: +"Sankey input: {nodes:[{name}],links:[{source,target,value}]}; links refer to node names. Use chartType:\"sankey\"." - removed
Input schema / properties / sankey / propertiesRemoved value: -{ - "links": { - "description": "Directed, value-weighted flows between nodes. Each (source, target) pair should be unique — a duplicate directed flow double-counts the link width. (Uniqueness is advisory for sankey; it is not warning-enforced.)", - "items": { - "additionalProperties": true, - "properties": { - "source": { - "minLength": 1, - "type": "string" - }, - "target": { - "minLength": 1, - "type": "string" - }, - "value": { - "type": "number" - } - }, - "required": [ - "source", - "target", - "value" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - }, - "nodes": { - "description": "Flow nodes. Each carries a unique 'name'; an optional numeric 'value' overrides the computed throughput.", - "items": { - "additionalProperties": true, - "properties": { - "name": { - "minLength": 1, - "type": "string" - }, - "value": { - "type": "number" - } - }, - "required": [ - "name" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - } -} - removed
Input schema / properties / sankey / requiredRemoved value: -[ - "nodes", - "links" -] - changed
Input schema / properties / strictFields / descriptionPrevious value: -"Strict field checks. When true, a data key that does not resolve is reported in warnings instead of producing a silently wrong chart: an encoding that names a field missing from every non-empty row (OODS-V131), or a choropleth region whose join key matches no map feature (OODS-V134, one per unmatched region). The default, false, keeps the current behavior, which drops unmatched map regions silently. Dashboard_render has its own strictFields, which turns OODS-V131 into an error panel through its onPanelError option."New value: +"Warn about unresolved fields and unmatched map joins (OODS-V131/V134). Default false preserves existing behavior." - removed
Input schema / titleRemoved value: -"Viz render input"
1 tool update
- Changed
tool_schema1 field changed- changed
Input schema / properties / name / enumPrevious value: -[ - "tokens_build", - "structured_data_fetch", - "brand_apply", - "brand_create", - "catalog_list", - "code_generate", - "design_compose", - "design_preview", - "pipeline_run", - "health_check", - "registry_snapshot", - "viz_render", - "dashboard_render", - "artifact_certify", - "fidelity_preview", - "component_map", - "schema_store", - "object_registry", - "schema_render", - "object_import", - "a11y_scan" -]New value: +[ + "tokens_build", + "structured_data_fetch", + "brand_apply", + "brand_create", + "brand_read", + "catalog_list", + "code_generate", + "design_compose", + "design_preview", + "design_versions", + "pipeline_run", + "health_check", + "registry_snapshot", + "viz_render", + "dashboard_render", + "artifact_certify", + "fidelity_preview", + "component_map", + "component_map_read", + "schema_store", + "schema_read", + "object_registry", + "object_register", + "schema_render", + "object_import", + "object_import_read", + "a11y_scan" +]
9 tool updates
- Changed
artifact_certify44 fields changed- changed
Input schema / $defs / colorEncodingBinding / oneOfPrevious value: -[ - { - "minLength": 1, - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "aggregate": { - "enum": [ - "sum", - "count", - "average", - "median", - "min", - "max", - "distinct" - ], - "type": "string" - }, - "field": { - "minLength": 1, - "type": "string" - }, - "range": { - "description": "Explicit hex colors for a nominal/ordinal color scale. Overrides the baked OODS categorical palette so an agent can supply its own scale (e.g. a 2-color presence scale). Applied in array order to the distinct series; a shorter range recycles (Vega domain[i]->range[i] mod len). Cartesian color only.", - "items": { - "pattern": "^#(?:[0-9a-fA-F]{3}){1,2}$", - "type": "string" - }, - "minItems": 2, - "type": "array" - }, - "scale": { - "enum": [ - "linear", - "temporal", - "log", - "sqrt", - "band", - "point", - "diverging" - ], - "type": "string" - }, - "sort": { - "oneOf": [ - { - "enum": [ - "none", - "ascending", - "descending" - ], - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "field": { - "type": "string" - }, - "order": { - "enum": [ - "ascending", - "descending" - ], - "type": "string" - } - }, - "required": [ - "field", - "order" - ], - "type": "object" - } - ] - }, - "timeUnit": { - "enum": [ - "year", - "quarter", - "month", - "week", - "day", - "hour", - "minute", - "second" - ], - "type": "string" - }, - "title": { - "type": "string" - }, - "type": { - "description": "Force the Vega-Lite/ECharts field type, overriding the engine's data-aware inference. Overrides the inferred field type.", - "enum": [ - "quantitative", - "temporal", - "ordinal", - "nominal" - ], - "type": "string" - } - }, - "required": [ - "field" - ], - "type": "object" - } -]New value: +[ + { + "minLength": 1, + "type": "string" + }, + { + "additionalProperties": false, + "properties": { + "aggregate": { + "enum": [ + "sum", + "count", + "average", + "median", + "min", + "max", + "distinct" + ], + "type": "string" + }, + "field": { + "minLength": 1, + "type": "string" + }, + "range": { + "description": "Explicit hex colors for a nominal/ordinal color scale. Overrides the baked OODS categorical palette so an agent can supply its own scale (e.g. a 2-color presence scale). Applied in array order to the distinct series; a shorter range recycles (Vega domain[i]->range[i] mod len). Cartesian color only.", + "items": { + "pattern": "^#(?:[0-9a-fA-F]{3}){1,2}$", + "type": "string" + }, + "minItems": 2, + "type": "array" + }, + "scale": { + "enum": [ + "linear", + "temporal", + "log", + "sqrt", + "band", + "point", + "diverging" + ], + "type": "string" + }, + "sort": { + "oneOf": [ + { + "enum": [ + "none", + "ascending", + "descending" + ], + "type": "string" + }, + { + "additionalProperties": false, + "properties": { + "field": { + "type": "string" + }, + "order": { + "enum": [ + "ascending", + "descending" + ], + "type": "string" + } + }, + "required": [ + "field", + "order" + ], + "type": "object" + } + ], + "type": [ + "string", + "object" + ] + }, + "timeUnit": { + "enum": [ + "year", + "quarter", + "month", + "week", + "day", + "hour", + "minute", + "second" + ], + "type": "string" + }, + "title": { + "type": "string" + }, + "type": { + "description": "Force the Vega-Lite/ECharts field type, overriding the engine's data-aware inference. Overrides the inferred field type.", + "enum": [ + "quantitative", + "temporal", + "ordinal", + "nominal" + ], + "type": "string" + } + }, + "required": [ + "field" + ], + "type": "object" + } +] - added
Input schema / $defs / colorEncodingBinding / typeAdded value: +[ + "string", + "object" +] - changed
Input schema / $defs / encodingBinding / oneOfPrevious value: -[ - { - "minLength": 1, - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "aggregate": { - "enum": [ - "sum", - "count", - "average", - "median", - "min", - "max", - "distinct" - ], - "type": "string" - }, - "currency": { - "description": "ISO 4217 code of the amounts this channel encodes, for example EUR. The labels print its en-US symbol where the format has \"$\" (EUR €, GBP £); without a format they read \"$,f\" ($12,000). One currency per chart.", - "pattern": "^[A-Za-z]{3}$", - "type": "string" - }, - "field": { - "minLength": 1, - "type": "string" - }, - "format": { - "description": "Label format of this channel's axis (x, y) or legend: a d3-format specifier such as \"$,f\" or \",.0f\" (d3-time-format for a temporal field). \"$\" prints the currency symbol: the currency's, else $. Without a precision, labels take the precision of the tick step, so neighbouring ticks never print the same text. Carried in the normalized spec, so artifact.certify replays it.", - "maxLength": 64, - "minLength": 1, - "type": "string" - }, - "scale": { - "enum": [ - "linear", - "temporal", - "log", - "sqrt", - "band", - "point", - "diverging" - ], - "type": "string" - }, - "sort": { - "oneOf": [ - { - "enum": [ - "none", - "ascending", - "descending" - ], - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "field": { - "type": "string" - }, - "order": { - "enum": [ - "ascending", - "descending" - ], - "type": "string" - } - }, - "required": [ - "field", - "order" - ], - "type": "object" - } - ] - }, - "timeUnit": { - "enum": [ - "year", - "quarter", - "month", - "week", - "day", - "hour", - "minute", - "second" - ], - "type": "string" - }, - "title": { - "type": "string" - }, - "type": { - "description": "Force the Vega-Lite/ECharts field type, overriding the engine's data-aware inference. Overrides the inferred field type.", - "enum": [ - "quantitative", - "temporal", - "ordinal", - "nominal" - ], - "type": "string" - } - }, - "required": [ - "field" - ], - "type": "object" - } -]New value: +[ + { + "minLength": 1, + "type": "string" + }, + { + "additionalProperties": false, + "properties": { + "aggregate": { + "enum": [ + "sum", + "count", + "average", + "median", + "min", + "max", + "distinct" + ], + "type": "string" + }, + "currency": { + "description": "ISO 4217 code of the amounts this channel encodes, for example EUR. The labels print its en-US symbol where the format has \"$\" (EUR €, GBP £); without a format they read \"$,f\" ($12,000). One currency per chart.", + "pattern": "^[A-Za-z]{3}$", + "type": "string" + }, + "field": { + "minLength": 1, + "type": "string" + }, + "format": { + "description": "Label format of this channel's axis (x, y) or legend: a d3-format specifier such as \"$,f\" or \",.0f\" (d3-time-format for a temporal field). \"$\" prints the currency symbol: the currency's, else $. Without a precision, labels take the precision of the tick step, so neighbouring ticks never print the same text. Carried in the normalized spec, so artifact_certify replays it.", + "maxLength": 64, + "minLength": 1, + "type": "string" + }, + "scale": { + "enum": [ + "linear", + "temporal", + "log", + "sqrt", + "band", + "point", + "diverging" + ], + "type": "string" + }, + "sort": { + "oneOf": [ + { + "enum": [ + "none", + "ascending", + "descending" + ], + "type": "string" + }, + { + "additionalProperties": false, + "properties": { + "field": { + "type": "string" + }, + "order": { + "enum": [ + "ascending", + "descending" + ], + "type": "string" + } + }, + "required": [ + "field", + "order" + ], + "type": "object" + } + ], + "type": [ + "string", + "object" + ] + }, + "timeUnit": { + "enum": [ + "year", + "quarter", + "month", + "week", + "day", + "hour", + "minute", + "second" + ], + "type": "string" + }, + "title": { + "type": "string" + }, + "type": { + "description": "Force the Vega-Lite/ECharts field type, overriding the engine's data-aware inference. Overrides the inferred field type.", + "enum": [ + "quantitative", + "temporal", + "ordinal", + "nominal" + ], + "type": "string" + } + }, + "required": [ + "field" + ], + "type": "object" + } +] - added
Input schema / $defs / encodingBinding / typeAdded value: +[ + "string", + "object" +] - added
Input schema / $defs / hierarchyNode / properties / children / items / typeAdded value: +"object" - removed
Input schema / properties / chart / $idRemoved value: -"https://designlab.local/schemas/viz.render.input.json" - removed
Input schema / properties / chart / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema" - changed
Input schema / properties / chart / properties / a11yEquivalence / descriptionPrevious value: -"A11y equivalence CERTIFY-AT-EMISSION switch. DEFAULT ON. The cartesian (Vega-Lite) emission is checked against the accessible-equivalence engine (validateVizEquivalenceRules): error-severity rules BLOCK (status:'error' with per-rule OODS-<rule.id> codes in `errors`), warn-severity failures surface in `warnings` as OODS-<rule.id>. Default builder output is conformant-BY-CONSTRUCTION , so generated specs pass; set false to opt out for agent-supplied non-conformant specs. Scoped to the cartesian path (the ECharts-primary scaffold has empty data and would spuriously fail data-equivalence rules)."New value: +"Checks the drawn chart's accessible equivalents as it is rendered; on by default. For Vega-Lite charts, a rule marked error stops the render (status error, with one OODS-<rule id> code per rule in errors), and a rule marked warn is reported in warnings. Charts built from rows and encodings always pass. Set false only for a spec you supply that is known not to conform. ECharts-primary charts are not checked here, because their scaffold has no data yet." - added
Input schema / properties / chart / properties / brand / descriptionAdded value: +"Token brand for drawing and certification." - changed
Input schema / properties / chart / properties / chord / descriptionPrevious value: -"Chord data for chartType 'chord' (explicit-only) — used INSTEAD of rows + x/y encodings. A native ECharts ribbon diagram: a ring of category arcs connected by weighted ribbons. Sankey-shaped — nodes plus value-weighted links; every link MUST carry a numeric 'value' (the ribbon width IS the flow magnitude) and reference existing node names — a link naming a node absent from 'nodes' fails loud (OODS-V147)."New value: +"Chord data for chartType 'chord' (explicit-only) — used instead of rows + x/y encodings. A native ECharts ribbon diagram: a ring of category arcs connected by weighted ribbons. Sankey-shaped — nodes plus value-weighted links; every link must carry a numeric 'value' (the ribbon width IS the flow magnitude) and reference existing node names — a link naming a node absent from 'nodes' fails loud (OODS-V147)." - changed
Input schema / properties / chart / properties / geo / descriptionPrevious value: -"Geo data for chartType 'choropleth', 'bubble_map', or 'flow_map' (explicit-only) — used INSTEAD of rows + x/y encodings. Carries INLINE geometry (a GeoJSON FeatureCollection in 'geojson', or a TopoJSON Topology in 'topojson' + 'topoObjectName'), an optional 'join' that merges tabular 'rows' into features by key, and the per-type encoding: 'valueField' colours regions for choropleth; 'longitudeField'/'latitudeField' (+ optional 'sizeField'/'colorField') place points for bubble_map; 'originLongitudeField'/'originLatitudeField'/'destinationLongitudeField'/'destinationLatitudeField' (+ optional 'strengthField'/'curvature') draw origin→destination ARCS for flow_map. Geometry is supplied INLINE — it is never fetched over the network. NOTE: geo specs are NOT self-contained (unlike treemap/sankey): the resolved FeatureCollection rides back on echartsSpec.__registration and the client re-registers the map by name before rendering. Geometry payloads can be large (a world atlas is ~100KB) — prefer a pre-simplified TopoJSON."New value: +"Geo data for chartType 'choropleth', 'bubble_map', or 'flow_map' (explicit-only) — used instead of rows + x/y encodings. Carries inline geometry (a GeoJSON FeatureCollection in 'geojson', or a TopoJSON Topology in 'topojson' + 'topoObjectName'), an optional 'join' that merges tabular 'rows' into features by key, and the per-type encoding: 'valueField' colours regions for choropleth; 'longitudeField'/'latitudeField' (+ optional 'sizeField'/'colorField') place points for bubble_map; 'originLongitudeField'/'originLatitudeField'/'destinationLongitudeField'/'destinationLatitudeField' (+ optional 'strengthField'/'curvature') draw origin→destination arcs for flow_map. Geometry is supplied inline — it is never fetched over the network. Note: geo specs are not self-contained (unlike treemap/sankey): the resolved FeatureCollection rides back on echartsSpec.__registration and the client re-registers the map by name before rendering. Geometry payloads can be large (a world atlas is ~100KB) — prefer a pre-simplified TopoJSON." - changed
Input schema / properties / chart / properties / geo / properties / destinationLatitudeField / descriptionPrevious value: -"Flow map: the row field holding the DESTINATION latitude. Required for flow_map."New value: +"Flow map: the row field holding the destination latitude. Required for flow_map." - changed
Input schema / properties / chart / properties / geo / properties / destinationLongitudeField / descriptionPrevious value: -"Flow map: the row field holding the DESTINATION longitude. Required for flow_map."New value: +"Flow map: the row field holding the destination longitude. Required for flow_map." - changed
Input schema / properties / chart / properties / geo / properties / originLatitudeField / descriptionPrevious value: -"Flow map: the row field holding the ORIGIN latitude. Required for flow_map."New value: +"Flow map: the row field holding the origin latitude. Required for flow_map." - changed
Input schema / properties / chart / properties / geo / properties / originLongitudeField / descriptionPrevious value: -"Flow map: the row field holding the ORIGIN longitude. Required for flow_map."New value: +"Flow map: the row field holding the origin longitude. Required for flow_map." - changed
Input schema / properties / chart / properties / hierarchy / descriptionPrevious value: -"Hierarchy data for chartType 'treemap' or 'sunburst' (explicit-only) — used INSTEAD of rows + x/y encodings. A discriminated union on 'type': 'adjacency_list' (flat nodes linked by parentId; a node whose parent is missing becomes its own root) or 'nested' (a single root node with children)."New value: +"Hierarchy data for chartType 'treemap' or 'sunburst' (explicit-only) — used instead of rows + x/y encodings. A discriminated union on 'type': 'adjacency_list' (flat nodes linked by parentId; a node whose parent is missing becomes its own root) or 'nested' (a single root node with children)." - changed
Input schema / properties / chart / properties / hierarchy / oneOfPrevious value: -[ - { - "additionalProperties": false, - "properties": { - "data": { - "description": "Flat node list. Each node carries id, parentId (null for roots), and a numeric value.", - "items": { - "additionalProperties": true, - "properties": { - "id": { - "minLength": 1, - "type": "string" - }, - "name": { - "type": "string" - }, - "parentId": { - "type": [ - "string", - "null" - ] - }, - "value": { - "type": "number" - } - }, - "required": [ - "id", - "parentId", - "value" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - }, - "type": { - "const": "adjacency_list" - } - }, - "required": [ - "type", - "data" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "data": { - "$ref": "#/$defs/hierarchyNode" - }, - "type": { - "const": "nested" - } - }, - "required": [ - "type", - "data" - ], - "type": "object" - } -]New value: +[ + { + "additionalProperties": false, + "properties": { + "data": { + "description": "Flat node list. Each node carries id, parentId (null for roots), and a numeric value.", + "items": { + "additionalProperties": true, + "properties": { + "id": { + "minLength": 1, + "type": "string" + }, + "name": { + "type": "string" + }, + "parentId": { + "type": [ + "string", + "null" + ] + }, + "value": { + "type": "number" + } + }, + "required": [ + "id", + "parentId", + "value" + ], + "type": "object" + }, + "minItems": 1, + "type": "array" + }, + "type": { + "const": "adjacency_list", + "type": "string" + } + }, + "required": [ + "type", + "data" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "data": { + "$ref": "#/$defs/hierarchyNode", + "type": "object" + }, + "type": { + "const": "nested", + "type": "string" + } + }, + "required": [ + "type", + "data" + ], + "type": "object" + } +] - added
Input schema / properties / chart / properties / hierarchy / typeAdded value: +"object" - changed
Input schema / properties / chart / properties / intent / descriptionPrevious value: -"STRUCTURED (typed, NOT free-text) visualization intent — the deterministic half of the NL→viz hand-off. Supply it INSTEAD of chartType/encodings (mutually exclusive with chartType): the named measures/dimensions drive ENCODING, `goal` + the data drive the recommender's chartType pick, an optional `chartFamily` post-filters that pick. Requires `rows`."New value: +"Structured (typed, not free-text) visualization intent — the deterministic half of the NL→viz hand-off. Supply it instead of chartType/encodings (mutually exclusive with chartType): the named measures/dimensions drive encoding, `goal` + the data drive the recommender's chartType pick, an optional `chartFamily` post-filters that pick. Requires `rows`." - changed
Input schema / properties / chart / properties / intent / properties / chartFamily / descriptionPrevious value: -"Optional preferred chart family. Post-filters the recommender ranking (NOT a scorer term) to this family, flagged lowConfidence when it was not the recommender's top pick. Constrained to the 5 TABULAR marks — the 8 explicit-only types are not recommender-rankable."New value: +"Optional preferred chart family. Post-filters the recommender ranking (not a scorer term) to this family, flagged lowConfidence when it was not the recommender's top pick. Constrained to the 5 tabular marks — the 8 explicit-only types are not recommender-rankable." - changed
Input schema / properties / chart / properties / intent / properties / dimensions / descriptionPrevious value: -"Named dimension fields (the breakdowns/axes); may be empty (e.g. a two-measure scatter). Each name MUST exist among the data rows' fields. `type` is RESERVED in v0.1 (field types infer from the data)."New value: +"Named dimension fields (the breakdowns/axes); may be empty (e.g. a two-measure scatter). Each name must exist among the data rows' fields. `type` is reserved in v0.1 (field types infer from the data)." - changed
Input schema / properties / chart / properties / intent / properties / measures / descriptionPrevious value: -"Named measure fields (the metrics to plot). Each name MUST exist among the data rows' fields. `type` is RESERVED in v0.1 (field types infer from the data)."New value: +"Named measure fields (the metrics to plot). Each name must exist among the data rows' fields. `type` is reserved in v0.1 (field types infer from the data)." - changed
Input schema / properties / chart / properties / network / descriptionPrevious value: -"Network data for chartType 'force_graph' (explicit-only) — used INSTEAD of rows + x/y encodings. Nodes (each with a unique 'id'; an optional 'group' drives category colour) and directed links (optional numeric 'value'). Every link MUST reference existing node ids — a link naming a node absent from 'nodes' fails loud (OODS-V147)."New value: +"Network data for chartType 'force_graph' (explicit-only) — used instead of rows + x/y encodings. Nodes (each with a unique 'id'; an optional 'group' drives category colour) and directed links (optional numeric 'value'). Every link must reference existing node ids — a link naming a node absent from 'nodes' fails loud (OODS-V147)." - changed
Input schema / properties / chart / properties / network / properties / links / descriptionPrevious value: -"Directed edges between nodes (an empty array is allowed for an all-isolated-nodes graph). Each 'source'/'target' MUST match a node 'id' (a dangling ref fails loud, OODS-V147). Directed: source→target and target→source are distinct edges. Each (source, target) pair should be unique — a duplicate directed edge double-counts and is flagged with a warning (OODS-V148)."New value: +"Directed edges between nodes (an empty array is allowed for an all-isolated-nodes graph). Each 'source'/'target' must match a node 'id' (a dangling ref fails loud, OODS-V147). Directed: source→target and target→source are distinct edges. Each (source, target) pair should be unique — a duplicate directed edge double-counts and is flagged with a warning (OODS-V148)." - added
Input schema / properties / chart / properties / output / descriptionAdded value: +"Optional drawing and accessibility outputs; the default reply contains hashes and certification." - added
Input schema / properties / chart / properties / output / properties / height / descriptionAdded value: +"Drawing height in pixels." - removed
Input schema / properties / chart / properties / output / properties / includeA11y / constRemoved value: -true - added
Input schema / properties / chart / properties / output / properties / includeA11y / defaultAdded value: +false - added
Input schema / properties / chart / properties / output / properties / includeA11y / descriptionAdded value: +"Include the accessible data table and narrative." - added
Input schema / properties / chart / properties / output / properties / includeA11y / typeAdded value: +"boolean" - removed
Input schema / properties / chart / properties / output / properties / includeNormalizedSpec / constRemoved value: -true - added
Input schema / properties / chart / properties / output / properties / includeNormalizedSpec / defaultAdded value: +false - added
Input schema / properties / chart / properties / output / properties / includeNormalizedSpec / descriptionAdded value: +"Include the normalized chart specification." - added
Input schema / properties / chart / properties / output / properties / includeNormalizedSpec / typeAdded value: +"boolean" - removed
Input schema / properties / chart / properties / output / properties / svg / constRemoved value: -true - added
Input schema / properties / chart / properties / output / properties / svg / defaultAdded value: +false - added
Input schema / properties / chart / properties / output / properties / svg / descriptionAdded value: +"Include the SVG drawing, for displaying the chart." - added
Input schema / properties / chart / properties / output / properties / svg / typeAdded value: +"boolean" - added
Input schema / properties / chart / properties / output / properties / width / descriptionAdded value: +"Drawing width in pixels." - changed
Input schema / properties / chart / properties / pattern / enumPrevious value: -[ - "pattern:viz:bubble-distribution", - "pattern:viz:correlation-matrix", - "pattern:viz:correlation-scatter", - "pattern:viz:detail-overview-bar", - "pattern:viz:diverging-bar", - "pattern:viz:drilldown-stacked-bar", - "pattern:viz:facet-small-multiples-line", - "pattern:viz:facet-target-band", - "pattern:viz:focus-context-line", - "pattern:viz:grouped-bar", - "pattern:viz:histogram", - "pattern:viz:layered-line-area", - "pattern:viz:multi-series-line", - "pattern:viz:running-total-area", - "pattern:viz:simple-bar", - "pattern:viz:sparkline-grid", - "pattern:viz:stacked-100-bar", - "pattern:viz:stacked-area-projection", - "pattern:viz:stacked-bar", - "pattern:viz:target-band-line", - "pattern:viz:time-grid-heatmap", - "pattern:viz:waterfall" -]New value: +[ + "pattern:viz:bubble-distribution", + "pattern:viz:correlation-matrix", + "pattern:viz:correlation-scatter", + "pattern:viz:detail-overview-bar", + "pattern:viz:diverging-bar", + "pattern:viz:drilldown-stacked-bar", + "pattern:viz:facet-small-multiples-line", + "pattern:viz:facet-target-band", + "pattern:viz:focus-context-line", + "pattern:viz:grouped-bar", + "pattern:viz:histogram", + "pattern:viz:layered-line-area", + "pattern:viz:multi-series-line", + "pattern:viz:running-total-area", + "pattern:viz:simple-bar", + "pattern:viz:stacked-100-bar", + "pattern:viz:stacked-area-projection", + "pattern:viz:stacked-bar", + "pattern:viz:target-band-line", + "pattern:viz:time-grid-heatmap", + "pattern:viz:waterfall" +] - changed
Input schema / properties / chart / properties / sankey / descriptionPrevious value: -"Flow data for chartType 'sankey' (explicit-only) — used INSTEAD of rows + x/y encodings. Nodes plus value-weighted links; every link MUST carry a numeric 'value' (the link width IS the flow magnitude) and reference existing node names."New value: +"Flow data for chartType 'sankey' (explicit-only) — used instead of rows + x/y encodings. Nodes plus value-weighted links; every link must carry a numeric 'value' (the link width IS the flow magnitude) and reference existing node names." - changed
Input schema / properties / chart / properties / strictFields / descriptionPrevious value: -"Field/key-presence STRICT switch. When true, a referenced data key that does not resolve is surfaced in `warnings` instead of a silent confident-wrong result: (m05) an explicit tabular chart whose encoding references a field ABSENT from every (non-empty) row → OODS-V131; (m06) a choropleth corridor whose join key has NO matching map feature → OODS-V134 (per unmatched corridor). DEFAULT false keeps today's behavior byte-identical (the geo silent-drop preserved). The dashboard.render strict check (its own `strictFields`) escalates V131 to an error panel via `onPanelError`."New value: +"Strict field checks. When true, a data key that does not resolve is reported in warnings instead of producing a silently wrong chart: an encoding that names a field missing from every non-empty row (OODS-V131), or a choropleth region whose join key matches no map feature (OODS-V134, one per unmatched region). The default, false, keeps the current behavior, which drops unmatched map regions silently. Dashboard_render has its own strictFields, which turns OODS-V131 into an error panel through its onPanelError option." - added
Input schema / properties / chart / properties / theme / descriptionAdded value: +"Colour theme for drawing and certification." - added
Input schema / properties / reproduceAdded value: +{ + "default": false, + "description": "Include the command and calls for reproducing this result.", + "type": "boolean" +}
- Changed
catalog_list2 fields changed- removed
Input schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema" - added
Input schema / properties / reproduceAdded value: +{ + "default": false, + "description": "Include the command and calls for reproducing this result.", + "type": "boolean" +}
- Changed
design_preview1 field changed- added
Input schema / properties / reproduceAdded value: +{ + "default": false, + "description": "Include the command and calls for reproducing this result.", + "type": "boolean" +}
- Changed
health_check2 fields changed- removed
Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#" - added
Input schema / properties / reproduceAdded value: +{ + "default": false, + "description": "Include the command and calls for reproducing this result.", + "type": "boolean" +}
- Changed
object_registry4 fields changed- removed
Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#" - added
Input schema / properties / action / typeAdded value: +"string" - added
Input schema / properties / reproduceAdded value: +{ + "default": false, + "description": "Include the command and calls for reproducing this result.", + "type": "boolean" +} - changed
Input schema / titlePrevious value: -"object input"New value: +"object_registry input"
- Changed
registry_snapshot4 fields changed- removed
Input schema / $idRemoved value: -"https://designlab.local/schemas/registry.snapshot.input.json" - removed
Input schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema" - added
Input schema / properties / reproduceAdded value: +{ + "default": false, + "description": "Include the command and calls for reproducing this result.", + "type": "boolean" +} - changed
Input schema / titlePrevious value: -"registry.snapshot input"New value: +"registry_snapshot input"
- Changed
structured_data_fetch6 fields changed- removed
Input schema / $idRemoved value: -"structuredData.fetch.input.json" - removed
Input schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema" - changed
Input schema / properties / dataset / enumPrevious value: -[ - "components", - "tokens", - "manifest" -]New value: +[ + "tokens", + "manifest" +] - removed
Input schema / properties / includeInternalRemoved value: -{ - "default": false, - "description": "Live components dataset only: also list OODS Foundry's internal (non-business) objects, after the business objects. Without it they are left out and registry.hiddenInternal counts them; a dated export is served unchanged.", - "type": "boolean" -} - added
Input schema / properties / reproduceAdded value: +{ + "default": false, + "description": "Include the command and calls for reproducing this result.", + "type": "boolean" +} - changed
Input schema / titlePrevious value: -"structuredData.fetch input"New value: +"structured_data_fetch input"
- Changed
tool_schema1 field changed- added
Input schema / properties / reproduceAdded value: +{ + "default": false, + "description": "Include the command and calls for reproducing this result.", + "type": "boolean" +}
- Changed
viz_render44 fields changed- changed
Input schema / $defs / colorEncodingBinding / oneOfPrevious value: -[ - { - "minLength": 1, - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "aggregate": { - "enum": [ - "sum", - "count", - "average", - "median", - "min", - "max", - "distinct" - ], - "type": "string" - }, - "field": { - "minLength": 1, - "type": "string" - }, - "range": { - "description": "Explicit hex colors for a nominal/ordinal color scale. Overrides the baked OODS categorical palette so an agent can supply its own scale (e.g. a 2-color presence scale). Applied in array order to the distinct series; a shorter range recycles (Vega domain[i]->range[i] mod len). Cartesian color only.", - "items": { - "pattern": "^#(?:[0-9a-fA-F]{3}){1,2}$", - "type": "string" - }, - "minItems": 2, - "type": "array" - }, - "scale": { - "enum": [ - "linear", - "temporal", - "log", - "sqrt", - "band", - "point", - "diverging" - ], - "type": "string" - }, - "sort": { - "oneOf": [ - { - "enum": [ - "none", - "ascending", - "descending" - ], - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "field": { - "type": "string" - }, - "order": { - "enum": [ - "ascending", - "descending" - ], - "type": "string" - } - }, - "required": [ - "field", - "order" - ], - "type": "object" - } - ] - }, - "timeUnit": { - "enum": [ - "year", - "quarter", - "month", - "week", - "day", - "hour", - "minute", - "second" - ], - "type": "string" - }, - "title": { - "type": "string" - }, - "type": { - "description": "Force the Vega-Lite/ECharts field type, overriding the engine's data-aware inference. Overrides the inferred field type.", - "enum": [ - "quantitative", - "temporal", - "ordinal", - "nominal" - ], - "type": "string" - } - }, - "required": [ - "field" - ], - "type": "object" - } -]New value: +[ + { + "minLength": 1, + "type": "string" + }, + { + "additionalProperties": false, + "properties": { + "aggregate": { + "enum": [ + "sum", + "count", + "average", + "median", + "min", + "max", + "distinct" + ], + "type": "string" + }, + "field": { + "minLength": 1, + "type": "string" + }, + "range": { + "description": "Explicit hex colors for a nominal/ordinal color scale. Overrides the baked OODS categorical palette so an agent can supply its own scale (e.g. a 2-color presence scale). Applied in array order to the distinct series; a shorter range recycles (Vega domain[i]->range[i] mod len). Cartesian color only.", + "items": { + "pattern": "^#(?:[0-9a-fA-F]{3}){1,2}$", + "type": "string" + }, + "minItems": 2, + "type": "array" + }, + "scale": { + "enum": [ + "linear", + "temporal", + "log", + "sqrt", + "band", + "point", + "diverging" + ], + "type": "string" + }, + "sort": { + "oneOf": [ + { + "enum": [ + "none", + "ascending", + "descending" + ], + "type": "string" + }, + { + "additionalProperties": false, + "properties": { + "field": { + "type": "string" + }, + "order": { + "enum": [ + "ascending", + "descending" + ], + "type": "string" + } + }, + "required": [ + "field", + "order" + ], + "type": "object" + } + ], + "type": [ + "string", + "object" + ] + }, + "timeUnit": { + "enum": [ + "year", + "quarter", + "month", + "week", + "day", + "hour", + "minute", + "second" + ], + "type": "string" + }, + "title": { + "type": "string" + }, + "type": { + "description": "Force the Vega-Lite/ECharts field type, overriding the engine's data-aware inference. Overrides the inferred field type.", + "enum": [ + "quantitative", + "temporal", + "ordinal", + "nominal" + ], + "type": "string" + } + }, + "required": [ + "field" + ], + "type": "object" + } +] - added
Input schema / $defs / colorEncodingBinding / typeAdded value: +[ + "string", + "object" +] - changed
Input schema / $defs / encodingBinding / oneOfPrevious value: -[ - { - "minLength": 1, - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "aggregate": { - "enum": [ - "sum", - "count", - "average", - "median", - "min", - "max", - "distinct" - ], - "type": "string" - }, - "currency": { - "description": "ISO 4217 code of the amounts this channel encodes, for example EUR. The labels print its en-US symbol where the format has \"$\" (EUR €, GBP £); without a format they read \"$,f\" ($12,000). One currency per chart.", - "pattern": "^[A-Za-z]{3}$", - "type": "string" - }, - "field": { - "minLength": 1, - "type": "string" - }, - "format": { - "description": "Label format of this channel's axis (x, y) or legend: a d3-format specifier such as \"$,f\" or \",.0f\" (d3-time-format for a temporal field). \"$\" prints the currency symbol: the currency's, else $. Without a precision, labels take the precision of the tick step, so neighbouring ticks never print the same text. Carried in the normalized spec, so artifact.certify replays it.", - "maxLength": 64, - "minLength": 1, - "type": "string" - }, - "scale": { - "enum": [ - "linear", - "temporal", - "log", - "sqrt", - "band", - "point", - "diverging" - ], - "type": "string" - }, - "sort": { - "oneOf": [ - { - "enum": [ - "none", - "ascending", - "descending" - ], - "type": "string" - }, - { - "additionalProperties": false, - "properties": { - "field": { - "type": "string" - }, - "order": { - "enum": [ - "ascending", - "descending" - ], - "type": "string" - } - }, - "required": [ - "field", - "order" - ], - "type": "object" - } - ] - }, - "timeUnit": { - "enum": [ - "year", - "quarter", - "month", - "week", - "day", - "hour", - "minute", - "second" - ], - "type": "string" - }, - "title": { - "type": "string" - }, - "type": { - "description": "Force the Vega-Lite/ECharts field type, overriding the engine's data-aware inference. Overrides the inferred field type.", - "enum": [ - "quantitative", - "temporal", - "ordinal", - "nominal" - ], - "type": "string" - } - }, - "required": [ - "field" - ], - "type": "object" - } -]New value: +[ + { + "minLength": 1, + "type": "string" + }, + { + "additionalProperties": false, + "properties": { + "aggregate": { + "enum": [ + "sum", + "count", + "average", + "median", + "min", + "max", + "distinct" + ], + "type": "string" + }, + "currency": { + "description": "ISO 4217 code of the amounts this channel encodes, for example EUR. The labels print its en-US symbol where the format has \"$\" (EUR €, GBP £); without a format they read \"$,f\" ($12,000). One currency per chart.", + "pattern": "^[A-Za-z]{3}$", + "type": "string" + }, + "field": { + "minLength": 1, + "type": "string" + }, + "format": { + "description": "Label format of this channel's axis (x, y) or legend: a d3-format specifier such as \"$,f\" or \",.0f\" (d3-time-format for a temporal field). \"$\" prints the currency symbol: the currency's, else $. Without a precision, labels take the precision of the tick step, so neighbouring ticks never print the same text. Carried in the normalized spec, so artifact_certify replays it.", + "maxLength": 64, + "minLength": 1, + "type": "string" + }, + "scale": { + "enum": [ + "linear", + "temporal", + "log", + "sqrt", + "band", + "point", + "diverging" + ], + "type": "string" + }, + "sort": { + "oneOf": [ + { + "enum": [ + "none", + "ascending", + "descending" + ], + "type": "string" + }, + { + "additionalProperties": false, + "properties": { + "field": { + "type": "string" + }, + "order": { + "enum": [ + "ascending", + "descending" + ], + "type": "string" + } + }, + "required": [ + "field", + "order" + ], + "type": "object" + } + ], + "type": [ + "string", + "object" + ] + }, + "timeUnit": { + "enum": [ + "year", + "quarter", + "month", + "week", + "day", + "hour", + "minute", + "second" + ], + "type": "string" + }, + "title": { + "type": "string" + }, + "type": { + "description": "Force the Vega-Lite/ECharts field type, overriding the engine's data-aware inference. Overrides the inferred field type.", + "enum": [ + "quantitative", + "temporal", + "ordinal", + "nominal" + ], + "type": "string" + } + }, + "required": [ + "field" + ], + "type": "object" + } +] - added
Input schema / $defs / encodingBinding / typeAdded value: +[ + "string", + "object" +] - added
Input schema / $defs / hierarchyNode / properties / children / items / typeAdded value: +"object" - removed
Input schema / $idRemoved value: -"https://designlab.local/schemas/viz.render.input.json" - removed
Input schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema" - changed
Input schema / properties / a11yEquivalence / descriptionPrevious value: -"A11y equivalence CERTIFY-AT-EMISSION switch. DEFAULT ON. The cartesian (Vega-Lite) emission is checked against the accessible-equivalence engine (validateVizEquivalenceRules): error-severity rules BLOCK (status:'error' with per-rule OODS-<rule.id> codes in `errors`), warn-severity failures surface in `warnings` as OODS-<rule.id>. Default builder output is conformant-BY-CONSTRUCTION , so generated specs pass; set false to opt out for agent-supplied non-conformant specs. Scoped to the cartesian path (the ECharts-primary scaffold has empty data and would spuriously fail data-equivalence rules)."New value: +"Checks the drawn chart's accessible equivalents as it is rendered; on by default. For Vega-Lite charts, a rule marked error stops the render (status error, with one OODS-<rule id> code per rule in errors), and a rule marked warn is reported in warnings. Charts built from rows and encodings always pass. Set false only for a spec you supply that is known not to conform. ECharts-primary charts are not checked here, because their scaffold has no data yet." - added
Input schema / properties / brand / descriptionAdded value: +"Token brand for drawing and certification." - changed
Input schema / properties / chord / descriptionPrevious value: -"Chord data for chartType 'chord' (explicit-only) — used INSTEAD of rows + x/y encodings. A native ECharts ribbon diagram: a ring of category arcs connected by weighted ribbons. Sankey-shaped — nodes plus value-weighted links; every link MUST carry a numeric 'value' (the ribbon width IS the flow magnitude) and reference existing node names — a link naming a node absent from 'nodes' fails loud (OODS-V147)."New value: +"Chord data for chartType 'chord' (explicit-only) — used instead of rows + x/y encodings. A native ECharts ribbon diagram: a ring of category arcs connected by weighted ribbons. Sankey-shaped — nodes plus value-weighted links; every link must carry a numeric 'value' (the ribbon width IS the flow magnitude) and reference existing node names — a link naming a node absent from 'nodes' fails loud (OODS-V147)." - changed
Input schema / properties / geo / descriptionPrevious value: -"Geo data for chartType 'choropleth', 'bubble_map', or 'flow_map' (explicit-only) — used INSTEAD of rows + x/y encodings. Carries INLINE geometry (a GeoJSON FeatureCollection in 'geojson', or a TopoJSON Topology in 'topojson' + 'topoObjectName'), an optional 'join' that merges tabular 'rows' into features by key, and the per-type encoding: 'valueField' colours regions for choropleth; 'longitudeField'/'latitudeField' (+ optional 'sizeField'/'colorField') place points for bubble_map; 'originLongitudeField'/'originLatitudeField'/'destinationLongitudeField'/'destinationLatitudeField' (+ optional 'strengthField'/'curvature') draw origin→destination ARCS for flow_map. Geometry is supplied INLINE — it is never fetched over the network. NOTE: geo specs are NOT self-contained (unlike treemap/sankey): the resolved FeatureCollection rides back on echartsSpec.__registration and the client re-registers the map by name before rendering. Geometry payloads can be large (a world atlas is ~100KB) — prefer a pre-simplified TopoJSON."New value: +"Geo data for chartType 'choropleth', 'bubble_map', or 'flow_map' (explicit-only) — used instead of rows + x/y encodings. Carries inline geometry (a GeoJSON FeatureCollection in 'geojson', or a TopoJSON Topology in 'topojson' + 'topoObjectName'), an optional 'join' that merges tabular 'rows' into features by key, and the per-type encoding: 'valueField' colours regions for choropleth; 'longitudeField'/'latitudeField' (+ optional 'sizeField'/'colorField') place points for bubble_map; 'originLongitudeField'/'originLatitudeField'/'destinationLongitudeField'/'destinationLatitudeField' (+ optional 'strengthField'/'curvature') draw origin→destination arcs for flow_map. Geometry is supplied inline — it is never fetched over the network. Note: geo specs are not self-contained (unlike treemap/sankey): the resolved FeatureCollection rides back on echartsSpec.__registration and the client re-registers the map by name before rendering. Geometry payloads can be large (a world atlas is ~100KB) — prefer a pre-simplified TopoJSON." - changed
Input schema / properties / geo / properties / destinationLatitudeField / descriptionPrevious value: -"Flow map: the row field holding the DESTINATION latitude. Required for flow_map."New value: +"Flow map: the row field holding the destination latitude. Required for flow_map." - changed
Input schema / properties / geo / properties / destinationLongitudeField / descriptionPrevious value: -"Flow map: the row field holding the DESTINATION longitude. Required for flow_map."New value: +"Flow map: the row field holding the destination longitude. Required for flow_map." - changed
Input schema / properties / geo / properties / originLatitudeField / descriptionPrevious value: -"Flow map: the row field holding the ORIGIN latitude. Required for flow_map."New value: +"Flow map: the row field holding the origin latitude. Required for flow_map." - changed
Input schema / properties / geo / properties / originLongitudeField / descriptionPrevious value: -"Flow map: the row field holding the ORIGIN longitude. Required for flow_map."New value: +"Flow map: the row field holding the origin longitude. Required for flow_map." - changed
Input schema / properties / hierarchy / descriptionPrevious value: -"Hierarchy data for chartType 'treemap' or 'sunburst' (explicit-only) — used INSTEAD of rows + x/y encodings. A discriminated union on 'type': 'adjacency_list' (flat nodes linked by parentId; a node whose parent is missing becomes its own root) or 'nested' (a single root node with children)."New value: +"Hierarchy data for chartType 'treemap' or 'sunburst' (explicit-only) — used instead of rows + x/y encodings. A discriminated union on 'type': 'adjacency_list' (flat nodes linked by parentId; a node whose parent is missing becomes its own root) or 'nested' (a single root node with children)." - changed
Input schema / properties / hierarchy / oneOfPrevious value: -[ - { - "additionalProperties": false, - "properties": { - "data": { - "description": "Flat node list. Each node carries id, parentId (null for roots), and a numeric value.", - "items": { - "additionalProperties": true, - "properties": { - "id": { - "minLength": 1, - "type": "string" - }, - "name": { - "type": "string" - }, - "parentId": { - "type": [ - "string", - "null" - ] - }, - "value": { - "type": "number" - } - }, - "required": [ - "id", - "parentId", - "value" - ], - "type": "object" - }, - "minItems": 1, - "type": "array" - }, - "type": { - "const": "adjacency_list" - } - }, - "required": [ - "type", - "data" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "data": { - "$ref": "#/$defs/hierarchyNode" - }, - "type": { - "const": "nested" - } - }, - "required": [ - "type", - "data" - ], - "type": "object" - } -]New value: +[ + { + "additionalProperties": false, + "properties": { + "data": { + "description": "Flat node list. Each node carries id, parentId (null for roots), and a numeric value.", + "items": { + "additionalProperties": true, + "properties": { + "id": { + "minLength": 1, + "type": "string" + }, + "name": { + "type": "string" + }, + "parentId": { + "type": [ + "string", + "null" + ] + }, + "value": { + "type": "number" + } + }, + "required": [ + "id", + "parentId", + "value" + ], + "type": "object" + }, + "minItems": 1, + "type": "array" + }, + "type": { + "const": "adjacency_list", + "type": "string" + } + }, + "required": [ + "type", + "data" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "data": { + "$ref": "#/$defs/hierarchyNode", + "type": "object" + }, + "type": { + "const": "nested", + "type": "string" + } + }, + "required": [ + "type", + "data" + ], + "type": "object" + } +] - added
Input schema / properties / hierarchy / typeAdded value: +"object" - changed
Input schema / properties / intent / descriptionPrevious value: -"STRUCTURED (typed, NOT free-text) visualization intent — the deterministic half of the NL→viz hand-off. Supply it INSTEAD of chartType/encodings (mutually exclusive with chartType): the named measures/dimensions drive ENCODING, `goal` + the data drive the recommender's chartType pick, an optional `chartFamily` post-filters that pick. Requires `rows`."New value: +"Structured (typed, not free-text) visualization intent — the deterministic half of the NL→viz hand-off. Supply it instead of chartType/encodings (mutually exclusive with chartType): the named measures/dimensions drive encoding, `goal` + the data drive the recommender's chartType pick, an optional `chartFamily` post-filters that pick. Requires `rows`." - changed
Input schema / properties / intent / properties / chartFamily / descriptionPrevious value: -"Optional preferred chart family. Post-filters the recommender ranking (NOT a scorer term) to this family, flagged lowConfidence when it was not the recommender's top pick. Constrained to the 5 TABULAR marks — the 8 explicit-only types are not recommender-rankable."New value: +"Optional preferred chart family. Post-filters the recommender ranking (not a scorer term) to this family, flagged lowConfidence when it was not the recommender's top pick. Constrained to the 5 tabular marks — the 8 explicit-only types are not recommender-rankable." - changed
Input schema / properties / intent / properties / dimensions / descriptionPrevious value: -"Named dimension fields (the breakdowns/axes); may be empty (e.g. a two-measure scatter). Each name MUST exist among the data rows' fields. `type` is RESERVED in v0.1 (field types infer from the data)."New value: +"Named dimension fields (the breakdowns/axes); may be empty (e.g. a two-measure scatter). Each name must exist among the data rows' fields. `type` is reserved in v0.1 (field types infer from the data)." - changed
Input schema / properties / intent / properties / measures / descriptionPrevious value: -"Named measure fields (the metrics to plot). Each name MUST exist among the data rows' fields. `type` is RESERVED in v0.1 (field types infer from the data)."New value: +"Named measure fields (the metrics to plot). Each name must exist among the data rows' fields. `type` is reserved in v0.1 (field types infer from the data)." - changed
Input schema / properties / network / descriptionPrevious value: -"Network data for chartType 'force_graph' (explicit-only) — used INSTEAD of rows + x/y encodings. Nodes (each with a unique 'id'; an optional 'group' drives category colour) and directed links (optional numeric 'value'). Every link MUST reference existing node ids — a link naming a node absent from 'nodes' fails loud (OODS-V147)."New value: +"Network data for chartType 'force_graph' (explicit-only) — used instead of rows + x/y encodings. Nodes (each with a unique 'id'; an optional 'group' drives category colour) and directed links (optional numeric 'value'). Every link must reference existing node ids — a link naming a node absent from 'nodes' fails loud (OODS-V147)." - changed
Input schema / properties / network / properties / links / descriptionPrevious value: -"Directed edges between nodes (an empty array is allowed for an all-isolated-nodes graph). Each 'source'/'target' MUST match a node 'id' (a dangling ref fails loud, OODS-V147). Directed: source→target and target→source are distinct edges. Each (source, target) pair should be unique — a duplicate directed edge double-counts and is flagged with a warning (OODS-V148)."New value: +"Directed edges between nodes (an empty array is allowed for an all-isolated-nodes graph). Each 'source'/'target' must match a node 'id' (a dangling ref fails loud, OODS-V147). Directed: source→target and target→source are distinct edges. Each (source, target) pair should be unique — a duplicate directed edge double-counts and is flagged with a warning (OODS-V148)." - added
Input schema / properties / output / descriptionAdded value: +"Optional drawing and accessibility outputs; the default reply contains hashes and certification." - added
Input schema / properties / output / properties / height / descriptionAdded value: +"Drawing height in pixels." - removed
Input schema / properties / output / properties / includeA11y / constRemoved value: -true - added
Input schema / properties / output / properties / includeA11y / defaultAdded value: +false - added
Input schema / properties / output / properties / includeA11y / descriptionAdded value: +"Include the accessible data table and narrative." - added
Input schema / properties / output / properties / includeA11y / typeAdded value: +"boolean" - removed
Input schema / properties / output / properties / includeNormalizedSpec / constRemoved value: -true - added
Input schema / properties / output / properties / includeNormalizedSpec / defaultAdded value: +false - added
Input schema / properties / output / properties / includeNormalizedSpec / descriptionAdded value: +"Include the normalized chart specification." - added
Input schema / properties / output / properties / includeNormalizedSpec / typeAdded value: +"boolean" - removed
Input schema / properties / output / properties / svg / constRemoved value: -true - added
Input schema / properties / output / properties / svg / defaultAdded value: +false - added
Input schema / properties / output / properties / svg / descriptionAdded value: +"Include the SVG drawing, for displaying the chart." - added
Input schema / properties / output / properties / svg / typeAdded value: +"boolean" - added
Input schema / properties / output / properties / width / descriptionAdded value: +"Drawing width in pixels." - changed
Input schema / properties / pattern / enumPrevious value: -[ - "pattern:viz:bubble-distribution", - "pattern:viz:correlation-matrix", - "pattern:viz:correlation-scatter", - "pattern:viz:detail-overview-bar", - "pattern:viz:diverging-bar", - "pattern:viz:drilldown-stacked-bar", - "pattern:viz:facet-small-multiples-line", - "pattern:viz:facet-target-band", - "pattern:viz:focus-context-line", - "pattern:viz:grouped-bar", - "pattern:viz:histogram", - "pattern:viz:layered-line-area", - "pattern:viz:multi-series-line", - "pattern:viz:running-total-area", - "pattern:viz:simple-bar", - "pattern:viz:sparkline-grid", - "pattern:viz:stacked-100-bar", - "pattern:viz:stacked-area-projection", - "pattern:viz:stacked-bar", - "pattern:viz:target-band-line", - "pattern:viz:time-grid-heatmap", - "pattern:viz:waterfall" -]New value: +[ + "pattern:viz:bubble-distribution", + "pattern:viz:correlation-matrix", + "pattern:viz:correlation-scatter", + "pattern:viz:detail-overview-bar", + "pattern:viz:diverging-bar", + "pattern:viz:drilldown-stacked-bar", + "pattern:viz:facet-small-multiples-line", + "pattern:viz:facet-target-band", + "pattern:viz:focus-context-line", + "pattern:viz:grouped-bar", + "pattern:viz:histogram", + "pattern:viz:layered-line-area", + "pattern:viz:multi-series-line", + "pattern:viz:running-total-area", + "pattern:viz:simple-bar", + "pattern:viz:stacked-100-bar", + "pattern:viz:stacked-area-projection", + "pattern:viz:stacked-bar", + "pattern:viz:target-band-line", + "pattern:viz:time-grid-heatmap", + "pattern:viz:waterfall" +] - added
Input schema / properties / reproduceAdded value: +{ + "default": false, + "description": "Include the command and calls for reproducing this result.", + "type": "boolean" +} - changed
Input schema / properties / sankey / descriptionPrevious value: -"Flow data for chartType 'sankey' (explicit-only) — used INSTEAD of rows + x/y encodings. Nodes plus value-weighted links; every link MUST carry a numeric 'value' (the link width IS the flow magnitude) and reference existing node names."New value: +"Flow data for chartType 'sankey' (explicit-only) — used instead of rows + x/y encodings. Nodes plus value-weighted links; every link must carry a numeric 'value' (the link width IS the flow magnitude) and reference existing node names." - changed
Input schema / properties / strictFields / descriptionPrevious value: -"Field/key-presence STRICT switch. When true, a referenced data key that does not resolve is surfaced in `warnings` instead of a silent confident-wrong result: (m05) an explicit tabular chart whose encoding references a field ABSENT from every (non-empty) row → OODS-V131; (m06) a choropleth corridor whose join key has NO matching map feature → OODS-V134 (per unmatched corridor). DEFAULT false keeps today's behavior byte-identical (the geo silent-drop preserved). The dashboard.render strict check (its own `strictFields`) escalates V131 to an error panel via `onPanelError`."New value: +"Strict field checks. When true, a data key that does not resolve is reported in warnings instead of producing a silently wrong chart: an encoding that names a field missing from every non-empty row (OODS-V131), or a choropleth region whose join key matches no map feature (OODS-V134, one per unmatched region). The default, false, keeps the current behavior, which drops unmatched map regions silently. Dashboard_render has its own strictFields, which turns OODS-V131 into an error panel through its onPanelError option." - added
Input schema / properties / theme / descriptionAdded value: +"Colour theme for drawing and certification."
2 tool updates
- Changed
catalog_list1 field changed- changed
Input schema / properties / category / descriptionPrevious value: -"Filter components by category (e.g., 'core', 'data')"New value: +"Filter components by category (e.g., 'core', 'lifecycle', 'visual')"
- Changed
registry_snapshot3 fields changed- changed
Input schema / descriptionPrevious value: -"Bulk-read recorded mappings plus live shipped and registered team traits and objects. Reports definition loader issues, including shadowed names. Draft preferred_terms, disambiguation_decisions and capabilities are not snapshot outputs."New value: +"Bulk-read recorded mappings plus live shipped and registered team traits and objects. Reports definition loader issues, including shadowed names. The default summary leaves out each trait's and object's schema, parameters, view extensions, semantics, tokens and metadata; detail full returns them, optionally only for named traits and objects. Draft preferred_terms, disambiguation_decisions and capabilities are not snapshot outputs." - added
Input schema / properties / detailAdded value: +{ + "default": "summary", + "description": "summary (default), or full definitions, best with names.", + "enum": [ + "summary", + "full" + ], + "type": "string" +} - added
Input schema / properties / namesAdded value: +{ + "description": "Exact trait and object names; misses go in notFound.", + "items": { + "minLength": 1, + "type": "string" + }, + "minItems": 1, + "type": "array", + "uniqueItems": true +}
5 tool updates
- Changed
artifact_certify12 fields changed- removed
Input schema / $defs / nonPatternInputRemoved value: -{ - "allOf": [ - { - "if": { - "properties": { - "chartType": { - "enum": [ - "bar", - "line", - "area", - "scatter", - "heatmap" - ] - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "properties": { - "encodings": { - "required": [ - "x", - "y" - ] - } - }, - "required": [ - "encodings" - ] - } - }, - { - "if": { - "properties": { - "chartType": { - "enum": [ - "treemap", - "sunburst" - ] - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "required": [ - "hierarchy" - ] - } - }, - { - "if": { - "properties": { - "chartType": { - "const": "sankey" - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "required": [ - "sankey" - ] - } - }, - { - "if": { - "properties": { - "chartType": { - "const": "force_graph" - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "required": [ - "network" - ] - } - }, - { - "if": { - "properties": { - "chartType": { - "const": "choropleth" - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "properties": { - "geo": { - "anyOf": [ - { - "required": [ - "geojson" - ] - }, - { - "required": [ - "topojson" - ] - } - ], - "required": [ - "valueField" - ] - } - }, - "required": [ - "geo" - ] - } - }, - { - "if": { - "properties": { - "chartType": { - "const": "bubble_map" - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "properties": { - "geo": { - "required": [ - "longitudeField", - "latitudeField", - "rows" - ] - } - }, - "required": [ - "geo" - ] - } - }, - { - "if": { - "properties": { - "chartType": { - "const": "flow_map" - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "properties": { - "geo": { - "anyOf": [ - { - "required": [ - "geojson" - ] - }, - { - "required": [ - "topojson" - ] - } - ], - "required": [ - "originLongitudeField", - "originLatitudeField", - "destinationLongitudeField", - "destinationLatitudeField", - "rows" - ] - } - }, - "required": [ - "geo" - ] - } - }, - { - "if": { - "properties": { - "chartType": { - "const": "chord" - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "required": [ - "chord" - ] - } - } - ], - "oneOf": [ - { - "required": [ - "rows" - ] - }, - { - "required": [ - "datasetRef" - ] - }, - { - "required": [ - "hierarchy" - ] - }, - { - "required": [ - "sankey" - ] - }, - { - "required": [ - "chord" - ] - }, - { - "required": [ - "network" - ] - }, - { - "required": [ - "geo" - ] - } - ] -} - removed
Input schema / properties / chart / allOfRemoved value: -[ - { - "if": { - "not": { - "required": [ - "pattern" - ] - } - }, - "then": { - "$ref": "#/$defs/nonPatternInput" - } - } -] - changed
Input schema / properties / chart / descriptionPrevious value: -"Render a real, data-bound visualization. Supply a registered pattern identity to preserve its source data and presentation, chartType + encodings for explicit mode, or rows/datasetRef for suggest or structured-intent mode. Retired patterns are not offered; structurally unsupported patterns return OODS-V167; pattern conflicts with explicit data, intent, or source identity/presentation overrides return OODS-V166. Brand, theme and output controls remain available."New value: +"Render a real, data-bound visualization. Supply a registered pattern identity to preserve its source data and presentation, chartType + encodings for explicit mode, or rows for suggest or structured-intent mode. Retired patterns are not offered; structurally unsupported patterns return OODS-V167; pattern conflicts with explicit data, intent, or source identity/presentation overrides return OODS-V166. Brand, theme and output controls remain available." - changed
Input schema / properties / chart / properties / chartType / descriptionPrevious value: -"Chart type. The tabular marks (bar->MarkBar, line->MarkLine, area->MarkArea, scatter->MarkPoint, heatmap->MarkRect) bind inline rows/datasetRef with x/y encodings. The hierarchy/flow/network/geo charts are explicit-only and return an ECharts option as the primary spec (no Vega-Lite equivalent): 'treemap' and 'sunburst' take the 'hierarchy' data branch; 'sankey' takes the 'sankey' data branch (nodes + value-weighted links); 'force_graph' takes the 'network' data branch (nodes + links); 'choropleth', 'bubble_map', and 'flow_map' take the 'geo' data branch (inline geometry + per-type encoding — flow_map draws origin→destination arcs); 'chord' takes the 'chord' data branch (sankey-shaped nodes + value-weighted links — a ring of category arcs joined by ribbons whose width is the value). Omit chartType to enter suggest mode (the recommender chooses a tabular type from the inferred field profiles)."New value: +"Chart type. The tabular marks (bar->MarkBar, line->MarkLine, area->MarkArea, scatter->MarkPoint, heatmap->MarkRect) bind inline rows with x/y encodings. The hierarchy/flow/network/geo charts are explicit-only and return an ECharts option as the primary spec (no Vega-Lite equivalent): 'treemap' and 'sunburst' take the 'hierarchy' data branch; 'sankey' takes the 'sankey' data branch (nodes + value-weighted links); 'force_graph' takes the 'network' data branch (nodes + links); 'choropleth', 'bubble_map', and 'flow_map' take the 'geo' data branch (inline geometry + per-type encoding — flow_map draws origin→destination arcs); 'chord' takes the 'chord' data branch (sankey-shaped nodes + value-weighted links — a ring of category arcs joined by ribbons whose width is the value). Omit chartType to enter suggest mode (the recommender chooses a tabular type from the inferred field profiles)." - changed
Input schema / properties / chart / properties / chord / descriptionPrevious value: -"Chord data for chartType 'chord' (explicit-only) — used INSTEAD of rows/datasetRef + x/y encodings. A native ECharts ribbon diagram: a ring of category arcs connected by weighted ribbons. Sankey-shaped — nodes plus value-weighted links; every link MUST carry a numeric 'value' (the ribbon width IS the flow magnitude) and reference existing node names — a link naming a node absent from 'nodes' fails loud (OODS-V147)."New value: +"Chord data for chartType 'chord' (explicit-only) — used INSTEAD of rows + x/y encodings. A native ECharts ribbon diagram: a ring of category arcs connected by weighted ribbons. Sankey-shaped — nodes plus value-weighted links; every link MUST carry a numeric 'value' (the ribbon width IS the flow magnitude) and reference existing node names — a link naming a node absent from 'nodes' fails loud (OODS-V147)." - changed
Input schema / properties / chart / properties / geo / descriptionPrevious value: -"Geo data for chartType 'choropleth', 'bubble_map', or 'flow_map' (explicit-only) — used INSTEAD of rows/datasetRef + x/y encodings. Carries INLINE geometry (a GeoJSON FeatureCollection in 'geojson', or a TopoJSON Topology in 'topojson' + 'topoObjectName'), an optional 'join' that merges tabular 'rows' into features by key, and the per-type encoding: 'valueField' colours regions for choropleth; 'longitudeField'/'latitudeField' (+ optional 'sizeField'/'colorField') place points for bubble_map; 'originLongitudeField'/'originLatitudeField'/'destinationLongitudeField'/'destinationLatitudeField' (+ optional 'strengthField'/'curvature') draw origin→destination ARCS for flow_map. Geometry is supplied INLINE — it is never fetched over the network. NOTE: geo specs are NOT self-contained (unlike treemap/sankey): the resolved FeatureCollection rides back on echartsSpec.__registration and the client re-registers the map by name before rendering. Geometry payloads can be large (a world atlas is ~100KB) — prefer a pre-simplified TopoJSON."New value: +"Geo data for chartType 'choropleth', 'bubble_map', or 'flow_map' (explicit-only) — used INSTEAD of rows + x/y encodings. Carries INLINE geometry (a GeoJSON FeatureCollection in 'geojson', or a TopoJSON Topology in 'topojson' + 'topoObjectName'), an optional 'join' that merges tabular 'rows' into features by key, and the per-type encoding: 'valueField' colours regions for choropleth; 'longitudeField'/'latitudeField' (+ optional 'sizeField'/'colorField') place points for bubble_map; 'originLongitudeField'/'originLatitudeField'/'destinationLongitudeField'/'destinationLatitudeField' (+ optional 'strengthField'/'curvature') draw origin→destination ARCS for flow_map. Geometry is supplied INLINE — it is never fetched over the network. NOTE: geo specs are NOT self-contained (unlike treemap/sankey): the resolved FeatureCollection rides back on echartsSpec.__registration and the client re-registers the map by name before rendering. Geometry payloads can be large (a world atlas is ~100KB) — prefer a pre-simplified TopoJSON." - changed
Input schema / properties / chart / properties / hierarchy / descriptionPrevious value: -"Hierarchy data for chartType 'treemap' or 'sunburst' (explicit-only) — used INSTEAD of rows/datasetRef + x/y encodings. A discriminated union on 'type': 'adjacency_list' (flat nodes linked by parentId; a node whose parent is missing becomes its own root) or 'nested' (a single root node with children)."New value: +"Hierarchy data for chartType 'treemap' or 'sunburst' (explicit-only) — used INSTEAD of rows + x/y encodings. A discriminated union on 'type': 'adjacency_list' (flat nodes linked by parentId; a node whose parent is missing becomes its own root) or 'nested' (a single root node with children)." - changed
Input schema / properties / chart / properties / intent / descriptionPrevious value: -"STRUCTURED (typed, NOT free-text) visualization intent — the deterministic half of the NL→viz hand-off. Supply it INSTEAD of chartType/encodings (mutually exclusive with chartType): the named measures/dimensions drive ENCODING, `goal` + the data drive the recommender's chartType pick, an optional `chartFamily` post-filters that pick, and an optional governed `measureRef` lights the governed-measure narrative overlay (only when output.includeA11y=true). Requires `rows` (or a `datasetRef`)."New value: +"STRUCTURED (typed, NOT free-text) visualization intent — the deterministic half of the NL→viz hand-off. Supply it INSTEAD of chartType/encodings (mutually exclusive with chartType): the named measures/dimensions drive ENCODING, `goal` + the data drive the recommender's chartType pick, an optional `chartFamily` post-filters that pick. Requires `rows`." - changed
Input schema / properties / chart / properties / network / descriptionPrevious value: -"Network data for chartType 'force_graph' (explicit-only) — used INSTEAD of rows/datasetRef + x/y encodings. Nodes (each with a unique 'id'; an optional 'group' drives category colour) and directed links (optional numeric 'value'). Every link MUST reference existing node ids — a link naming a node absent from 'nodes' fails loud (OODS-V147)."New value: +"Network data for chartType 'force_graph' (explicit-only) — used INSTEAD of rows + x/y encodings. Nodes (each with a unique 'id'; an optional 'group' drives category colour) and directed links (optional numeric 'value'). Every link MUST reference existing node ids — a link naming a node absent from 'nodes' fails loud (OODS-V147)." - changed
Input schema / properties / chart / properties / pattern / descriptionPrevious value: -"Exact versioned pattern source identity. Renderable patterns preserve source rows, identity, presentation and accessibility metadata. Retired identities are not offered (their reasons are in the viz taxonomy). Structurally unsupported scenes return OODS-V167. Static SVG shows the default selection state (OODS-V175). Cannot be combined with chartType, encodings, rows, datasetRef, intent, hierarchy, sankey, chord, network, geo, id, name, description or opacity (OODS-V166)."New value: +"Exact versioned pattern source identity. Renderable patterns preserve source rows, identity, presentation and accessibility metadata. Retired identities are not offered (their reasons are in the viz taxonomy). Structurally unsupported scenes return OODS-V167. Static SVG shows the default selection state (OODS-V175). Cannot be combined with chartType, encodings, rows, intent, hierarchy, sankey, chord, network, geo, id, name, description or opacity (OODS-V166)." - changed
Input schema / properties / chart / properties / rows / maxItemsPrevious value: -5000New value: +500 - changed
Input schema / properties / chart / properties / sankey / descriptionPrevious value: -"Flow data for chartType 'sankey' (explicit-only) — used INSTEAD of rows/datasetRef + x/y encodings. Nodes plus value-weighted links; every link MUST carry a numeric 'value' (the link width IS the flow magnitude) and reference existing node names."New value: +"Flow data for chartType 'sankey' (explicit-only) — used INSTEAD of rows + x/y encodings. Nodes plus value-weighted links; every link MUST carry a numeric 'value' (the link width IS the flow magnitude) and reference existing node names."
- Changed
design_preview3 fields changed- added
Input schema / properties / context / descriptionAdded value: +"The context the screen was composed for." - added
Input schema / properties / framework / descriptionAdded value: +"The framework of the generated app." - added
Input schema / properties / object / descriptionAdded value: +"An object with recorded screens at this version."
- Changed
object_registry8 fields changed- added
Input schema / additionalPropertiesAdded value: +false - removed
Input schema / allOfRemoved value: -[ - { - "if": { - "properties": { - "action": { - "const": "list" - } - }, - "required": [ - "action" - ] - }, - "then": { - "additionalProperties": false, - "properties": { - "action": { - "const": "list" - }, - "domain": { - "description": "Filter to objects in a specific domain (e.g. 'core.identity', 'saas.billing')", - "type": "string" - }, - "includeInternal": { - "default": false, - "description": "Also list OODS Foundry's internal (non-business) objects, after the business objects. Without it they are left out and hiddenInternal counts them.", - "type": "boolean" - }, - "maturity": { - "description": "Filter by metadata maturity level", - "enum": [ - "draft", - "alpha", - "beta", - "stable" - ], - "type": "string" - }, - "trait": { - "description": "Filter to objects composing a given trait (e.g. 'Priceable', 'lifecycle/Stateful')", - "type": "string" - } - }, - "type": "object" - } - }, - { - "if": { - "properties": { - "action": { - "const": "show" - } - }, - "required": [ - "action" - ] - }, - "then": { - "additionalProperties": false, - "properties": { - "action": { - "const": "show" - }, - "context": { - "description": "Optional: filter view_extensions to a single context (e.g. 'detail', 'list', 'form', 'timeline', 'card', 'inline')", - "type": "string" - }, - "name": { - "description": "Object name to look up (e.g. 'User', 'Product', 'Invoice')", - "pattern": "^[A-Za-z][A-Za-z0-9_-]*$", - "type": "string" - } - }, - "required": [ - "name" - ], - "type": "object" - } - } -] - added
Input schema / properties / contextAdded value: +{ + "description": "Optional: filter view_extensions to a single context (e.g. 'detail', 'list', 'form', 'timeline', 'card', 'inline')", + "type": "string" +} - added
Input schema / properties / domainAdded value: +{ + "description": "Filter to objects in a specific domain (e.g. 'core.identity', 'saas.billing')", + "type": "string" +} - added
Input schema / properties / includeInternalAdded value: +{ + "default": false, + "description": "Also list OODS Foundry's internal (non-business) objects, after the business objects. Without it they are left out and hiddenInternal counts them.", + "type": "boolean" +} - added
Input schema / properties / maturityAdded value: +{ + "description": "Filter by metadata maturity level", + "enum": [ + "draft", + "alpha", + "beta", + "stable" + ], + "type": "string" +} - added
Input schema / properties / nameAdded value: +{ + "description": "Object name to look up (e.g. 'User', 'Product', 'Invoice')", + "pattern": "^[A-Za-z][A-Za-z0-9_-]*$", + "type": "string" +} - added
Input schema / properties / traitAdded value: +{ + "description": "Filter to objects composing a given trait (e.g. 'Priceable', 'lifecycle/Stateful')", + "type": "string" +}
- Changed
tool_schema2 fields changed- added
Input schema / properties / kind / descriptionAdded value: +"The tool's input schema or its output schema." - added
Input schema / properties / name / descriptionAdded value: +"Any OODS Foundry tool at this version, local-only tools included."
- Changed
viz_render12 fields changed- removed
Input schema / $defs / nonPatternInputRemoved value: -{ - "allOf": [ - { - "if": { - "properties": { - "chartType": { - "enum": [ - "bar", - "line", - "area", - "scatter", - "heatmap" - ] - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "properties": { - "encodings": { - "required": [ - "x", - "y" - ] - } - }, - "required": [ - "encodings" - ] - } - }, - { - "if": { - "properties": { - "chartType": { - "enum": [ - "treemap", - "sunburst" - ] - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "required": [ - "hierarchy" - ] - } - }, - { - "if": { - "properties": { - "chartType": { - "const": "sankey" - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "required": [ - "sankey" - ] - } - }, - { - "if": { - "properties": { - "chartType": { - "const": "force_graph" - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "required": [ - "network" - ] - } - }, - { - "if": { - "properties": { - "chartType": { - "const": "choropleth" - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "properties": { - "geo": { - "anyOf": [ - { - "required": [ - "geojson" - ] - }, - { - "required": [ - "topojson" - ] - } - ], - "required": [ - "valueField" - ] - } - }, - "required": [ - "geo" - ] - } - }, - { - "if": { - "properties": { - "chartType": { - "const": "bubble_map" - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "properties": { - "geo": { - "required": [ - "longitudeField", - "latitudeField", - "rows" - ] - } - }, - "required": [ - "geo" - ] - } - }, - { - "if": { - "properties": { - "chartType": { - "const": "flow_map" - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "properties": { - "geo": { - "anyOf": [ - { - "required": [ - "geojson" - ] - }, - { - "required": [ - "topojson" - ] - } - ], - "required": [ - "originLongitudeField", - "originLatitudeField", - "destinationLongitudeField", - "destinationLatitudeField", - "rows" - ] - } - }, - "required": [ - "geo" - ] - } - }, - { - "if": { - "properties": { - "chartType": { - "const": "chord" - } - }, - "required": [ - "chartType" - ] - }, - "then": { - "required": [ - "chord" - ] - } - } - ], - "oneOf": [ - { - "required": [ - "rows" - ] - }, - { - "required": [ - "datasetRef" - ] - }, - { - "required": [ - "hierarchy" - ] - }, - { - "required": [ - "sankey" - ] - }, - { - "required": [ - "chord" - ] - }, - { - "required": [ - "network" - ] - }, - { - "required": [ - "geo" - ] - } - ] -} - removed
Input schema / allOfRemoved value: -[ - { - "if": { - "not": { - "required": [ - "pattern" - ] - } - }, - "then": { - "$ref": "#/$defs/nonPatternInput" - } - } -] - changed
Input schema / descriptionPrevious value: -"Render a real, data-bound visualization. Supply a registered pattern identity to preserve its source data and presentation, chartType + encodings for explicit mode, or rows/datasetRef for suggest or structured-intent mode. Retired patterns are not offered; structurally unsupported patterns return OODS-V167; pattern conflicts with explicit data, intent, or source identity/presentation overrides return OODS-V166. Brand, theme and output controls remain available."New value: +"Render a real, data-bound visualization. Supply a registered pattern identity to preserve its source data and presentation, chartType + encodings for explicit mode, or rows for suggest or structured-intent mode. Retired patterns are not offered; structurally unsupported patterns return OODS-V167; pattern conflicts with explicit data, intent, or source identity/presentation overrides return OODS-V166. Brand, theme and output controls remain available." - changed
Input schema / properties / chartType / descriptionPrevious value: -"Chart type. The tabular marks (bar->MarkBar, line->MarkLine, area->MarkArea, scatter->MarkPoint, heatmap->MarkRect) bind inline rows/datasetRef with x/y encodings. The hierarchy/flow/network/geo charts are explicit-only and return an ECharts option as the primary spec (no Vega-Lite equivalent): 'treemap' and 'sunburst' take the 'hierarchy' data branch; 'sankey' takes the 'sankey' data branch (nodes + value-weighted links); 'force_graph' takes the 'network' data branch (nodes + links); 'choropleth', 'bubble_map', and 'flow_map' take the 'geo' data branch (inline geometry + per-type encoding — flow_map draws origin→destination arcs); 'chord' takes the 'chord' data branch (sankey-shaped nodes + value-weighted links — a ring of category arcs joined by ribbons whose width is the value). Omit chartType to enter suggest mode (the recommender chooses a tabular type from the inferred field profiles)."New value: +"Chart type. The tabular marks (bar->MarkBar, line->MarkLine, area->MarkArea, scatter->MarkPoint, heatmap->MarkRect) bind inline rows with x/y encodings. The hierarchy/flow/network/geo charts are explicit-only and return an ECharts option as the primary spec (no Vega-Lite equivalent): 'treemap' and 'sunburst' take the 'hierarchy' data branch; 'sankey' takes the 'sankey' data branch (nodes + value-weighted links); 'force_graph' takes the 'network' data branch (nodes + links); 'choropleth', 'bubble_map', and 'flow_map' take the 'geo' data branch (inline geometry + per-type encoding — flow_map draws origin→destination arcs); 'chord' takes the 'chord' data branch (sankey-shaped nodes + value-weighted links — a ring of category arcs joined by ribbons whose width is the value). Omit chartType to enter suggest mode (the recommender chooses a tabular type from the inferred field profiles)." - changed
Input schema / properties / chord / descriptionPrevious value: -"Chord data for chartType 'chord' (explicit-only) — used INSTEAD of rows/datasetRef + x/y encodings. A native ECharts ribbon diagram: a ring of category arcs connected by weighted ribbons. Sankey-shaped — nodes plus value-weighted links; every link MUST carry a numeric 'value' (the ribbon width IS the flow magnitude) and reference existing node names — a link naming a node absent from 'nodes' fails loud (OODS-V147)."New value: +"Chord data for chartType 'chord' (explicit-only) — used INSTEAD of rows + x/y encodings. A native ECharts ribbon diagram: a ring of category arcs connected by weighted ribbons. Sankey-shaped — nodes plus value-weighted links; every link MUST carry a numeric 'value' (the ribbon width IS the flow magnitude) and reference existing node names — a link naming a node absent from 'nodes' fails loud (OODS-V147)." - changed
Input schema / properties / geo / descriptionPrevious value: -"Geo data for chartType 'choropleth', 'bubble_map', or 'flow_map' (explicit-only) — used INSTEAD of rows/datasetRef + x/y encodings. Carries INLINE geometry (a GeoJSON FeatureCollection in 'geojson', or a TopoJSON Topology in 'topojson' + 'topoObjectName'), an optional 'join' that merges tabular 'rows' into features by key, and the per-type encoding: 'valueField' colours regions for choropleth; 'longitudeField'/'latitudeField' (+ optional 'sizeField'/'colorField') place points for bubble_map; 'originLongitudeField'/'originLatitudeField'/'destinationLongitudeField'/'destinationLatitudeField' (+ optional 'strengthField'/'curvature') draw origin→destination ARCS for flow_map. Geometry is supplied INLINE — it is never fetched over the network. NOTE: geo specs are NOT self-contained (unlike treemap/sankey): the resolved FeatureCollection rides back on echartsSpec.__registration and the client re-registers the map by name before rendering. Geometry payloads can be large (a world atlas is ~100KB) — prefer a pre-simplified TopoJSON."New value: +"Geo data for chartType 'choropleth', 'bubble_map', or 'flow_map' (explicit-only) — used INSTEAD of rows + x/y encodings. Carries INLINE geometry (a GeoJSON FeatureCollection in 'geojson', or a TopoJSON Topology in 'topojson' + 'topoObjectName'), an optional 'join' that merges tabular 'rows' into features by key, and the per-type encoding: 'valueField' colours regions for choropleth; 'longitudeField'/'latitudeField' (+ optional 'sizeField'/'colorField') place points for bubble_map; 'originLongitudeField'/'originLatitudeField'/'destinationLongitudeField'/'destinationLatitudeField' (+ optional 'strengthField'/'curvature') draw origin→destination ARCS for flow_map. Geometry is supplied INLINE — it is never fetched over the network. NOTE: geo specs are NOT self-contained (unlike treemap/sankey): the resolved FeatureCollection rides back on echartsSpec.__registration and the client re-registers the map by name before rendering. Geometry payloads can be large (a world atlas is ~100KB) — prefer a pre-simplified TopoJSON." - changed
Input schema / properties / hierarchy / descriptionPrevious value: -"Hierarchy data for chartType 'treemap' or 'sunburst' (explicit-only) — used INSTEAD of rows/datasetRef + x/y encodings. A discriminated union on 'type': 'adjacency_list' (flat nodes linked by parentId; a node whose parent is missing becomes its own root) or 'nested' (a single root node with children)."New value: +"Hierarchy data for chartType 'treemap' or 'sunburst' (explicit-only) — used INSTEAD of rows + x/y encodings. A discriminated union on 'type': 'adjacency_list' (flat nodes linked by parentId; a node whose parent is missing becomes its own root) or 'nested' (a single root node with children)." - changed
Input schema / properties / intent / descriptionPrevious value: -"STRUCTURED (typed, NOT free-text) visualization intent — the deterministic half of the NL→viz hand-off. Supply it INSTEAD of chartType/encodings (mutually exclusive with chartType): the named measures/dimensions drive ENCODING, `goal` + the data drive the recommender's chartType pick, an optional `chartFamily` post-filters that pick, and an optional governed `measureRef` lights the governed-measure narrative overlay (only when output.includeA11y=true). Requires `rows` (or a `datasetRef`)."New value: +"STRUCTURED (typed, NOT free-text) visualization intent — the deterministic half of the NL→viz hand-off. Supply it INSTEAD of chartType/encodings (mutually exclusive with chartType): the named measures/dimensions drive ENCODING, `goal` + the data drive the recommender's chartType pick, an optional `chartFamily` post-filters that pick. Requires `rows`." - changed
Input schema / properties / network / descriptionPrevious value: -"Network data for chartType 'force_graph' (explicit-only) — used INSTEAD of rows/datasetRef + x/y encodings. Nodes (each with a unique 'id'; an optional 'group' drives category colour) and directed links (optional numeric 'value'). Every link MUST reference existing node ids — a link naming a node absent from 'nodes' fails loud (OODS-V147)."New value: +"Network data for chartType 'force_graph' (explicit-only) — used INSTEAD of rows + x/y encodings. Nodes (each with a unique 'id'; an optional 'group' drives category colour) and directed links (optional numeric 'value'). Every link MUST reference existing node ids — a link naming a node absent from 'nodes' fails loud (OODS-V147)." - changed
Input schema / properties / pattern / descriptionPrevious value: -"Exact versioned pattern source identity. Renderable patterns preserve source rows, identity, presentation and accessibility metadata. Retired identities are not offered (their reasons are in the viz taxonomy). Structurally unsupported scenes return OODS-V167. Static SVG shows the default selection state (OODS-V175). Cannot be combined with chartType, encodings, rows, datasetRef, intent, hierarchy, sankey, chord, network, geo, id, name, description or opacity (OODS-V166)."New value: +"Exact versioned pattern source identity. Renderable patterns preserve source rows, identity, presentation and accessibility metadata. Retired identities are not offered (their reasons are in the viz taxonomy). Structurally unsupported scenes return OODS-V167. Static SVG shows the default selection state (OODS-V175). Cannot be combined with chartType, encodings, rows, intent, hierarchy, sankey, chord, network, geo, id, name, description or opacity (OODS-V166)." - changed
Input schema / properties / rows / maxItemsPrevious value: -5000New value: +500 - changed
Input schema / properties / sankey / descriptionPrevious value: -"Flow data for chartType 'sankey' (explicit-only) — used INSTEAD of rows/datasetRef + x/y encodings. Nodes plus value-weighted links; every link MUST carry a numeric 'value' (the link width IS the flow magnitude) and reference existing node names."New value: +"Flow data for chartType 'sankey' (explicit-only) — used INSTEAD of rows + x/y encodings. Nodes plus value-weighted links; every link MUST carry a numeric 'value' (the link width IS the flow magnitude) and reference existing node names."
1 tool update
- Changed
tool_schema1 field changed- changed
Input schema / properties / name / enumPrevious value: -[ - "tokens_build", - "structured_data_fetch", - "brand_apply", - "brand_create", - "catalog_list", - "code_generate", - "design_compose", - "design_preview", - "pipeline_run", - "health_check", - "registry_snapshot", - "viz_render", - "dashboard_render", - "artifact_certify", - "fidelity_preview", - "component_map", - "schema_store", - "object_registry", - "schema_render", - "a11y_scan" -]New value: +[ + "tokens_build", + "structured_data_fetch", + "brand_apply", + "brand_create", + "catalog_list", + "code_generate", + "design_compose", + "design_preview", + "pipeline_run", + "health_check", + "registry_snapshot", + "viz_render", + "dashboard_render", + "artifact_certify", + "fidelity_preview", + "component_map", + "schema_store", + "object_registry", + "schema_render", + "object_import", + "a11y_scan" +]
7 tool updates
- Removed
health - Added
health_check - Removed
object - Added
object_registry - Added
structured_data_fetch - Removed
structuredData_fetch - Changed
tool_schema1 field changed- changed
Input schema / properties / name / enumPrevious value: -[ - "tokens_build", - "structuredData_fetch", - "brand_apply", - "brand_intake", - "catalog_list", - "code_generate", - "design_compose", - "design_preview", - "pipeline", - "health", - "registry_snapshot", - "viz_render", - "dashboard_render", - "artifact_certify", - "fidelity_preview", - "map", - "schema", - "object", - "repl", - "a11y_scan" -]New value: +[ + "tokens_build", + "structured_data_fetch", + "brand_apply", + "brand_create", + "catalog_list", + "code_generate", + "design_compose", + "design_preview", + "pipeline_run", + "health_check", + "registry_snapshot", + "viz_render", + "dashboard_render", + "artifact_certify", + "fidelity_preview", + "component_map", + "schema_store", + "object_registry", + "schema_render", + "a11y_scan" +]
9 tool updates
- First observed
artifact_certify - First observed
catalog_list - First observed
design_preview - First observed
health - First observed
object - First observed
registry_snapshot - First observed
structuredData_fetch - First observed
tool_schema - First observed
viz_render
Related MCP Connectors
Access and maintain design system docs, tokens, components, skills, and contexts across any project.
Provides style context & tokens to design or restyle web UIs in any framework
Orvain UI design system for React and Vue: real component props, variants and tokens for AI tools
Build and manage your design system with AI: tokens, themes, components, icons, Figma and code.
Related MCP Servers
- AlicenseAqualityAmaintenanceEnables high-craft web design and engineering through OKLCH color systems, fluid typography, Three.js 3D scenes, frontend security audits, multi-viewport capture, and Python-backed design verification.1112 npmMIT
- AlicenseBqualityCmaintenanceEnables LLMs to work with the Optics Design System, providing access to 83 design tokens (HSL-based colors, spacing, typography), 24 components with dependencies, and tools for theme generation, accessibility checking, and code scaffolding.154 npm1MIT
- AlicenseAqualityCmaintenanceProvides 1000+ handcrafted design system themes (colors, typography, components, animations) to inject into AI-generated UI, enabling tools like Claude, ChatGPT, and Cursor to produce polished, non-generic interfaces.27 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to generate complete, deterministic design systems from a single brand color — harmonious palettes, font pairings, type and spacing scales, elevation shadows, responsive grids, motion presets, dark-mode themes, and WCAG contrast audits — and export them as CSS, JSON, Tailwind, or SCSS through natural conversation.1054 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.