SeedWeaver
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEEDWEAVER_LICENSE | No | License key for SeedWeaver Pro, required to unlock unlimited tables and rows. |
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 |
|---|---|
| analyze_schemaA | Parse a database schema (SQL CREATE TABLE statements or a JSON schema) and report its tables, columns, relationships, and the order seed data would be generated in. Use this first to confirm SeedWeaver understands the schema correctly. |
| generate_seed_dataA | Generate realistic, referentially-coherent test data from a database schema. Foreign keys resolve to real generated primary keys, unique constraints are respected, and values are realistic (names, emails, dates). Accepts SQL DDL or a JSON schema. Returns INSERT statements, JSON, or CSV. |
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 2 tools
The two tools have entirely distinct purposes: one for analyzing/validating schema understanding, the other for generating data. No overlap or ambiguity.
Both tools follow the consistent verb_noun pattern (analyze_schema, generate_seed_data), making their actions and targets clear.
With only 2 tools, the server is minimal but still covers its core purpose. It could benefit from a few more tools (e.g., configuration, validation), but the count is acceptable for a focused utility.
The tool surface covers the essential workflow: analyze schema, then generate data. Minor gaps like customizing data types or revalidating are absent but not critical for the stated purpose.