Skip to main content
Glama
seedfast-ai

Seedfast MCP Server

Official
by seedfast-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

seedfast_schema_info

Inspect a PostgreSQL database schema to list tables, columns, primary and foreign keys, and approximate row counts, enabling a precise scope for seeding test data.

Instructions

Introspects a PostgreSQL database schema — lists tables, columns, primary keys, foreign keys, and approximate row counts. Returns a JSON object with a tables array; each entry has name (schema-qualified), columns (name, data_type, nullable, default), primary_key, foreign_keys (columns, references_table, references_columns), and approximate_row_count. Row counts come from pg_class.reltuples and are APPROXIMATE — they may be stale between ANALYZEs and may be -1 on never-analyzed tables. Implementation invokes seedfast schema --json as a subprocess with a 30s timeout. Call this before writing a scope description — it helps you understand table relationships and size so you can craft a precise scope; especially useful for large databases where you want to target specific tables. Does not require SEEDFAST_API_KEY. The dsn argument is optional — when omitted, the server falls back to SEEDFAST_DSN or DATABASE_URL from its environment. Next: use the schema info to write a scope string, then call seedfast_plan with that scope. For scope-writing guidance, also request the scope-examples prompt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dsnNoPostgreSQL connection string. When omitted, the MCP server falls back to SEEDFAST_DSN, then DATABASE_URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.6.4

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden and does substantial work: it states the output shape, that row counts are approximate and may be stale or -1 before ANALYZE, that a subprocess with a 30s timeout is used, and that no SEEDFAST_API_KEY is required. It does not state side effects explicitly, but 'Introspects' implies a read-only operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is longer than average but every sentence adds value: return format, approximation caveat, implementation timeout, auth requirement, usage context, and next steps. It is front-loaded with the core purpose and logically progresses from what to when to how.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations and no output schema, the description is remarkably complete: it documents return structure, row-count accuracy caveats, execution timeout, environment fallbacks, and downstream workflow guidance. An agent has everything necessary to call it correctly and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole parameter dsn is already fully documented in the schema (100% coverage), so the baseline is 3. The description reinforces optionality and the fallback order (SEEDFAST_DSN, then DATABASE_URL), adding modest clarity but no wholly new semantic information beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb ('Introspects') and resource ('PostgreSQL database schema'), then enumerates exactly what is listed (tables, columns, keys, row counts). This clearly distinguishes it from sibling planning/run tools, which operate on scopes and executions rather than database introspection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says 'Call this before writing a scope description' and gives a concrete next step: use the schema info to write a scope, then call seedfast_plan. It also notes when it is especially useful (large databases targeting specific tables). It does not name alternatives to avoid, but the sequencing guidance is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools