Skip to main content
Glama
rgrz

PeopleSoft MCP Server

by rgrz

get_translate_values

Decode PeopleSoft field codes by retrieving valid translate values and their short and long descriptions for any field name.

Instructions

    Get all valid translate values for a PeopleSoft field.
    
    Many PeopleSoft fields use single or double letter codes that have
    specific meanings. This tool decodes those values.
    
    Common examples:
    - SEX: 'M' = Male, 'F' = Female
    - HR_STATUS: 'A' = Active, 'I' = Inactive
    - EMPL_STATUS: 'A' = Active, 'T' = Terminated, 'L' = Leave, etc.
    - MAR_STATUS: 'S' = Single, 'M' = Married, 'D' = Divorced
    
    :param field_name: The field name to look up (e.g., 'SEX', 'HR_STATUS', 'EMPL_STATUS')
    :return: List of valid values with their short and long descriptions
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
field_nameYes
Behavior3/5

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

No annotations are provided, so the description must cover behavioral aspects. It notes that the tool returns a list of valid values with descriptions, which is sufficient for a read-only operation. However, it does not disclose any potential side effects, authorization requirements, or rate limits, which would improve transparency.

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 concise and to the point, with a clear opening sentence followed by examples. It uses a structured format with parameter documentation. While it could be slightly more front-loaded, there is no unnecessary content.

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 tool's simplicity (one parameter, no output schema), the description adequately explains the functionality and provides common use cases. It covers the essential information needed for an AI agent to understand and invoke the tool correctly. Minor gaps like missing output format details don't detract significantly.

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?

The schema has 0% description coverage, but the description provides parameter documentation in reStructuredText format, stating the parameter is the field name and giving examples. This adds significant meaning beyond the schema's mere type definition, compensating for the lack of schema descriptions.

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

Purpose4/5

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

The description clearly states the verb 'Get' and the resource 'valid translate values for a PeopleSoft field', making the purpose obvious. However, it does not explicitly differentiate from the sibling 'get_translate_field_values', which may be similar. The examples help clarify what it does.

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

Usage Guidelines3/5

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

The description provides examples and implies the tool is for decoding field codes, but it does not explicitly state when to use this tool versus alternatives, nor does it provide any exclusions or prerequisites. The context is clear but lacks direct guidance.

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