nteract/semiotic
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getSchemaA | Return the prop schema for a Semiotic chart component. Pass { component: '' } to get its props, or omit component to list all available components. Components marked [renderable] can be passed to renderChart for static SVG output. |
| suggestChartA | Recommend Semiotic chart types for a given data sample. Pass { data: [...] } with 1-5 sample objects. Optionally pass intent to narrow suggestions. Returns ranked recommendations with example props. |
| renderChartB | Render a Semiotic chart to static SVG. Returns SVG string or validation errors. Available components: AreaChart, BarChart, BoxPlot, BubbleChart, ChordDiagram, ChoroplethMap, CirclePack, ConnectedScatterplot, DistanceCartogram, DonutChart, DotPlot, FlowMap, ForceDirectedGraph, GroupedBarChart, Heatmap, LineChart, OrbitDiagram, PieChart, ProportionalSymbolMap, SankeyDiagram, Scatterplot, StackedAreaChart, StackedBarChart, SwarmPlot, TreeDiagram, Treemap. |
| diagnoseConfigA | Diagnose a Semiotic chart configuration for common problems (empty data, bad dimensions, missing accessors, wrong data shape, etc). Returns a human-readable diagnostic report with actionable fixes. |
| reportIssueA | Generate a GitHub issue URL for Semiotic bug reports or feature requests. Returns a URL the user can open to submit. For rendering bugs, include the component name, props summary, and any diagnoseConfig output in the body. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: diagnoseConfig for configuration validation, getSchema for component schema retrieval, renderChart for SVG chart generation, reportIssue for GitHub issue creation, and suggestChart for chart type recommendations. There is no overlap or ambiguity in their functions.
The naming follows a consistent verb_noun pattern (e.g., diagnoseConfig, getSchema, renderChart, reportIssue, suggestChart), with all tools using camelCase. However, the pattern is slightly inconsistent as some tools use verb+noun (e.g., renderChart) while others use verb+noun combinations that are less standard (e.g., diagnoseConfig, reportIssue), but overall it remains readable and predictable.
With 5 tools, this server is well-scoped for its purpose of chart configuration and rendering in Semiotic. Each tool serves a specific role in the workflow, from diagnosis and schema retrieval to rendering and issue reporting, making the count appropriate and efficient.
The tool surface covers the core chart lifecycle: diagnosis, schema exploration, rendering, issue reporting, and chart type suggestion. Minor gaps exist, such as the lack of tools for updating or deleting chart configurations, but these are not critical for the server's stated purpose, and agents can work around them effectively.