Skip to main content
Glama
rgrz

PeopleSoft MCP Server

by rgrz

list_calendar_runs

View payroll calendar runs and their status. Filter by pay entity, year, or status to narrow results.

Instructions

    List payroll calendar runs with their status.
    
    :param pay_entity: Optional filter by pay entity
    :param year: Optional filter by year
    :param status: Optional filter by status ('open', 'closed', 'finalized')
    :param limit: Maximum results (default 20)
    :return: List of calendar runs
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNo
limitNo
statusNo
pay_entityNo
Behavior2/5

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

No annotations are provided, and the description only states 'list' without disclosing read-only nature, potential for large data, or any side effects. It fails to clarify that this is a safe, non-destructive operation.

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, front-loading the purpose in the first sentence, and listing parameters in a structured docstring format. No superfluous content.

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

Completeness3/5

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

Given no output schema, the description does not specify the return format beyond 'list of calendar runs'. It covers parameters adequately but lacks guidance on pagination, ordering, or performance considerations.

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?

All four parameters are explained with clear roles (e.g., 'Optional filter by status'), adding meaning beyond the input schema which lacks descriptions. The status parameter includes example values, enhancing understanding.

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 'List payroll calendar runs with their status', a specific verb-resource pair. It distinguishes from sibling tools like get_payroll_results or search_employees by being a distinct listing tool.

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?

No explicit when-to-use or when-not-to guidance. The parameter list implies filtering capabilities but doesn't direct the agent to alternatives or clarify when this tool is preferable over similar list or search tools.

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