Skip to main content
Glama
rgrz

PeopleSoft MCP Server

by rgrz

query_peoplesoft_db

Execute SQL queries on PeopleSoft Oracle database to retrieve employee, payroll, or benefits data. Automatically follows best practices by checking table structure and code translations for accurate results.

Instructions

Query PeopleSoft Oracle Database directly.

When working with a PeopleSoft database, follow these guidelines in order:

1. FIRST, always check the record structure and fields:
   - Use: SELECT RECNAME, FIELDNAME FROM PSRECFIELD WHERE RECNAME = 'YOUR_TABLE'
   - This shows all fields in a record/table and helps prevent invalid field errors

2. SECOND, check field properties and translations:
   - For field details: SELECT * FROM PSDBFIELD WHERE FIELDNAME = 'YOUR_FIELD'
   - For code translations: 
       * ALWAYS check PSXLATITEM and PSXLATITEMLANG for single/double letter codes
       * Example: 'M'/'F' for SEX, 'SP'/'C' for RELATIONSHIP, 'Y'/'N' for flags
       * Query: SELECT FIELDNAME, FIELDVALUE, XLATLONGNAME, XLATSHORTNAME 
               FROM PSXLATITEM 
               WHERE FIELDNAME = 'YOUR_FIELD'
   - Understanding field properties ensures correct data handling

3. THIRD, review table indexes for performance:
   - Use: SELECT * FROM PSKEYDEFN WHERE RECNAME = 'YOUR_TABLE'
   - Knowing indexes helps write efficient queries using indexed fields

4. FINALLY, write your query using the discovered structure
   - Example finding employee data:
     1. Check PSRECFIELD for PS_PERSONAL_DATA fields
     2. Look up important fields in PSDBFIELD
     3. Check PSKEYDEFN for PS_PERSONAL_DATA indexes
     4. Write optimized query using indexed fields
     5. Don't forget to join with PSXLATITEM for any code fields

AVAILABLE RESOURCES:
- Use describe_table() to get table structure
- Use list_tables() to search for tables
- Use get_translate_values() to decode field codes
- Use get_table_indexes() for performance optimization

:param sql_query: SQL query to execute (e.g., SELECT * FROM PS_EMPLOYEE WHERE EMPLID = :1)
:param parameters: List of query parameters (optional)
:return: A dictionary containing query results or an error message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sql_queryYes
parametersNo
Behavior3/5

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

With no annotations, the description must carry the burden of behavioral disclosure. It explains the query execution and safe usage workflow, but does not explicitly state whether the tool is read-only, what permissions are needed, or potential risks (e.g., DML statements could modify data).

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

Conciseness3/5

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

The description is verbose with multiple numbered steps and repeated examples. While structured, it could be more concise without losing essential guidance. The front-loaded sentence clearly states the tool's purpose.

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

Completeness4/5

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

Given the complexity of direct SQL querying in PeopleSoft, the description provides a thorough workflow, links to companion tools, and explains the return type generically. However, it lacks a detailed output format specification, which would be expected without an output schema.

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

Parameters4/5

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

Despite 0% schema coverage, the description includes a dedicated param section with examples (e.g., 'SELECT * FROM PS_EMPLOYEE WHERE EMPLID = :1') and explains the optional parameter list, adding meaning 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 clearly states the tool's function: 'Query PeopleSoft Oracle Database directly.' It distinguishes itself from sibling tools like get_employee or search_records by offering direct SQL execution, and the step-by-step guidelines reinforce its purpose.

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

Usage Guidelines5/5

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

The description provides a prioritized workflow (FIRST, SECOND, THIRD, FINALLY) and explicitly lists alternative tools (describe_table, list_tables, get_translate_values, get_table_indexes) for preliminary steps, telling the agent when to use each.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rgrz/peoplesoft-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server