wrds
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WRDS_OUTPUT_DIR | No | Directory where exports and the query log are written. If unset, exports and the query log go to ~/wrds-data. | ~/wrds-data |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_librariesA | List WRDS libraries this account can access, with the vendor and whether data rows may be returned to the AI under the WRDS AI policy. Optional substring filter. |
| list_tablesB | List tables in a WRDS library with approximate row counts. |
| describe_tableB | Show columns, types and WRDS column descriptions (where available) for a table. |
| search_catalogB | Search table names, column names and column descriptions across all accessible libraries for a keyword (e.g. 'revenue', 'nace', 'sic', 'orbis'). Use this first to answer 'is X available?' questions. |
| check_availabilityA | Run an aggregate-only availability check (counts, distinct counts, min/max years) on any accessible library, including ones where row-level data is not AI-allowed. The query must return a single summary row, e.g. SELECT count(*), count(distinct gvkey), min(fyear), max(fyear) FROM comp.g_funda WHERE ... |
| queryA | Run a read-only SELECT and return up to |
| export_queryA | Run a read-only SELECT with no row limit and save it to the output folder (default ~/wrds-data). fmt: csv, parquet or xlsx. Returns the path, row count and columns; a 5-row preview is included only for AI-allowed sources. |
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 7 tools
The tools are clearly divided into metadata discovery (list_libraries, list_tables, describe_table, search_catalog) and data access (check_availability, query, export_query). Within each group, purposes are distinct, with check_availability explicitly aggregate-only and query/export_query differentiated by output destination and row limits. No two tools appear to do the same thing.
All tool names use snake_case, and most follow a verb_noun pattern (e.g., list_libraries, describe_table, export_query). The tool 'query' is a lone verb without a noun, a minor deviation from the otherwise consistent pattern.
Seven tools is well-scoped for a read-only data access server, covering discovery and retrieval without bloat. Each tool earns its place and none feel redundant.
The set covers the full read-only data lifecycle: discovering libraries, tables, and columns; searching across catalogs; checking availability under AI policy; and running bounded or unbounded queries. No obvious gaps exist for the stated domain.