Skip to main content
Glama
rgrz

PeopleSoft MCP Server

by rgrz

get_table_indexes

Retrieve index keys for any PeopleSoft table to write efficient queries by using indexed fields in WHERE clauses and understanding the logical key structure.

Instructions

    Get the index keys for a PeopleSoft table to help write efficient queries.
    
    Understanding indexes helps you:
    - Write WHERE clauses that use indexed fields for better performance
    - Understand the logical key structure of a table
    - Know which fields uniquely identify a row
    
    Common PeopleSoft key patterns:
    - Simple: EMPLID (employee ID only)
    - Effective-dated: EMPLID, EMPL_RCD, EFFDT, EFFSEQ
    - SetID-based: SETID, DEPTID, EFFDT
    
    :param table_name: The PeopleSoft record name (e.g., 'JOB', 'PERSONAL_DATA')
    :return: List of indexes with their key fields
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
table_nameYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses a read-only intent (getting indexes) and return type (list of indexes with key fields), but lacks details on authorization, rate limits, or side effects. Somewhat adequate but could be richer.

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 well-structured with sections (purpose, benefits, patterns, param doc). It front-loads the main action. However, it is slightly verbose with explanatory text that could be streamlined, earning a 4 rather than 5.

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 low schema coverage and no output schema, the description provides adequate completeness: explains the tool's value, common patterns, and return content. It could specify the return structure more precisely, but the examples help.

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?

With 0% schema description coverage, the description adds meaningful context for the single parameter 'table_name' by providing examples like 'JOB', 'PERSONAL_DATA'. This clarifies the expected input beyond the schema's bare type definition.

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 'Get the index keys for a PeopleSoft table' with a specific verb and resource. It distinguishes from sibling tools like 'describe_table' or 'get_record_definition' by focusing specifically on indexes for query optimization.

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?

The description provides clear context on when to use the tool (writing efficient queries) and lists common key patterns. It does not explicitly mention when not to use or alternatives, but the context is sufficient for selection among siblings.

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