Ross ERP Data Dictionary
Server Details
Structure-only reference for the vanilla Ross ERP 8.0 schema, UI menu tree, and program catalog.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 21 tools
Most tools are clearly partitioned by domain (schema, programs, facilities, search, stats) and by list/lookup/reverse-lookup intent, so an agent can generally choose correctly. A few near-overlaps exist—find_column vs search_columns and get_ddl vs lookup_table—but their descriptions explain the different granularity and output.
The set mostly follows clear patterns: list_* for browsing, lookup_* for details, search_* for searching, and *_stats for overviews. Minor deviations like find_column, get_ddl, and the noun_noun reverse-pair names (facility_programs vs program_facilities) break the otherwise consistent verb-first convention, but the naming remains predictable and readable.
21 tools is on the heavy side for what is ultimately a read-only metadata dictionary, falling into the 16–25 range that feels borderline. Each tool has a distinct role, so the count is not chaotic, but the surface could likely be trimmed by consolidating some search and lookup variants.
The tool surface covers the full read-only data-dictionary workflow: orientation stats, browsing and filtering, detailed lookup, cross-domain search, DDL retrieval, reverse references between tables/programs/facilities, and graph traversal. There are no obvious dead ends—list tools point to lookup tools, and reverse lookups complete the relationship coverage.
Available Tools
21 toolsfacility_programsAInspect
Cross-link a UI facility to the program(s) that implement it — 'what code runs this screen?'. Each program carries a match label: declared (named by the facility's menu entry, authoritative) or titleId (TITLE id equals the facility code). Complements lookup_facility (which gives the facility's tables and call graph). Metadata only — no source body.
Inputs: code (required).
facility_statsAInspect
Overview of the Ross ERP 8.0 application layer — the client menu tree of UI facilities (screens, reports, inquiries, maintenance functions): total facilities, and their breakdown by system (e.g. ACCOUNTS_PAYABLE), database (FIN/MAN) and class (REPORT, MAINTENANCE, INQUIRY, ...). Use this first to orient before browsing facilities.
Inputs: no named parameters.
find_columnAInspect
Look up a single column by exact name across the whole Ross ERP 8.0 schema: its description, valid values, notes, every table that carries it, and any foreign-key roles it plays.
Inputs: name (required).
get_ddlBInspect
Return the CREATE TABLE (DDL) for a Ross ERP 8.0 table, with column descriptions as comments plus primary-key and foreign-key constraints.
Inputs: name (required).
graph_neighborsAInspect
List the knowledge-graph neighbours of an object — the programs, tables, views and procedures directly connected to it, with relationship type and direction.
Inputs: name (required), limit.
list_facilitiesAInspect
Browse and filter Ross ERP 8.0 UI facilities (menu screens/functions). Filter by system, database, class, a name/code substring, or withTables (only facilities whose table cluster is known); paginate with limit/offset. Returns summaries — use lookup_facility for full detail.
Inputs: q, class, limit, offset, +3 more.
list_objectsAInspect
Browse and filter Ross ERP 8.0 objects (tables / views / procedures / functions). Filter by type, database, module, or a name substring; paginate with limit/offset. Returns object summaries — use lookup_table for full detail.
Inputs: q, db, type, limit, +2 more.
list_programsAInspect
Browse and filter Ross ERP 8.0 programs (application source, metadata only). Filter by module (ap, gl, ic, sop, ...), type (a=archive, i=inquiry, m=maintenance, r=report, s=server, l=load, u=utility, ...), layer (base | vendor-core), titled (only programs that declare a TITLE id), or a substring of basename/title; paginate with limit/offset. Returns summaries — use lookup_program for full detail.
Inputs: q, type, layer, limit, +3 more.
lookup_facilityAInspect
Full detail for one Ross ERP 8.0 UI facility by code: its name, system, database, class, GEMBASE program, help text, menu paths, the physical table cluster it touches — core (the working set the screen is built on) and reference (control/lookup tables) — and its call graph: the facilities this one invokes (calls) and the facilities that invoke it (calledBy), parsed from the program source.
Inputs: code (required).
lookup_programAInspect
Full detail for one Ross ERP 8.0 program, by TITLE program-id (e.g. AP_A_002) or source basename (e.g. ap_a_check_register): its module, type, layer, declared title, internal PROCEDURE_FORM procedures, the Data Dictionary tables it references — each classified read vs read-write (a write is a FIND IN.../LOCK=WRITE update, an ADD, or a DELETE) with a writeCount — its call graph (the programs it invokes and the programs that invoke it, from PERFORM "GEM:"), the menu facilities it backs, and — for programs with no TITLE label — a display name carried from the menu facility's registry description. Metadata only — no source body.
Inputs: id (required).
lookup_tableAInspect
Full schema for a Ross ERP 8.0 object (table / view / procedure / function): columns with type, nullability, keys, descriptions and valid values, foreign keys in and out, related tables, and usage.
Inputs: name (required).
path_betweenAInspect
Find the shortest path between two objects in the Ross ERP 8.0 knowledge graph (how A reaches B through calls / references / accesses).
Inputs: to (required), from (required).
program_facilitiesAInspect
Reverse of facility_programs: which UI facilities (menu screens / reports / inquiries) a program backs — 'what screens does this program run?'. One program often serves several facilities. Lookup by TITLE id (e.g. AP_I_001) or basename (e.g. ap_i_vendors); each facility carries the same declared / titleId match label.
Inputs: id (required).
program_statsAInspect
Overview of the Ross ERP 8.0 program catalog — every application-source program (metadata only, no source body): total programs, how many declare a TITLE id, how many carry Data Dictionary table links, total program→table edges, read/write counts (withWrites programs, writeEdges program→table write edges), base vs vendor-core split, program→program call-graph counts (programs with outbound calls, total call edges) and how many back a menu facility, plus the module and type breakdowns. Use this first to orient before browsing programs.
Inputs: no named parameters.
schema_statsAInspect
Overview of the Ross ERP 8.0 schema in one call: object counts by type, module list, total/distinct columns, audit-twin pairs, and the top tables/columns/modules. Use this first to orient before drilling in.
Inputs: no named parameters.
search_allAInspect
Cross-domain search in one call — spans schema objects, columns, UI facilities and programs at once. Use this when you don't yet know which layer a term lives in (e.g. 'check register' is a screen, a program and a table). Scope to one layer with type = object | column | facility | program (default all); limit is per domain.
Inputs: query (required), type, limit.
search_columnsBInspect
Search the Ross ERP 8.0 schema by name (and column descriptions). Returns matching objects and columns.
Inputs: query (required), limit.
search_facilitiesAInspect
Search Ross ERP 8.0 UI facilities by code, name, help text, program or tag. Use this to find the screen/report for a task, e.g. 'check register' or 'purchase order receipts'.
Inputs: query (required), limit.
search_programsAInspect
Search Ross ERP 8.0 programs by basename, TITLE program-id, title, module or type. Use this to find the program behind a task, e.g. 'check register' or 'ap_a'.
Inputs: query (required), limit.
table_facilitiesAInspect
Reverse lookup: which UI facilities (screens/reports/programs) touch a given Ross ERP 8.0 table — split into core (facilities whose working set includes it) and reference (facilities that use it as a control/lookup), each with how many times the program source accesses it. Answers 'what screens read or write this table?'.
Inputs: table (required).
table_programsAInspect
Reverse lookup: which standard Ross ERP 8.0 programs reference a given table (validated against the Data Dictionary). Answers 'what code touches this table?' — complements table_facilities (which answers 'what screens touch it?'). Metadata only — no source body.
Inputs: table (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Nori ERP reports: data dictionary, read-only SQL, saved reports and PDF print formats.
Read-only Interlude and High Five NPC, loot, Soul Crystal and XP reference tools.
2,000+ MCP servers read at source level. Know what one does before you connect. Free, no key.
Read-only U.S. lab-test catalog, collection-site search, and reference-range context.
Related MCP Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants such as Claude, Cursor, and Windsurf to query and operate a cloud ERP through natural language, exposing 87 tools spanning purchasing, sales, inventory, manufacturing, costing, assets, auditing, and financial reporting. Supports read-only queries plus create, submit, audit, and reverse-audit operations with metadata exploration, SQL Server schema probing, and optional HTTP/SSE remote deployment.-
- FlicenseAqualityDmaintenanceA static, read-only MCP server that exposes a database knowledge base (schema, relationships, workflows, and reasoning patterns) so Claude Code / Copilot can reason about a database without a live connection.10-
- FlicenseNot gradedqualityCmaintenanceStandalone read-only MCP server for browsing Oracle HDL business object metadata. Provides tools to search and retrieve catalog entries, components, and attributes from a local repository.-
- AlicenseAqualityDmaintenanceA read-only MCP server that provides AI coding tools with database schema structure (tables, columns, keys, relationships) without exposing row data.324 PyPIApache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.