Skip to main content
Glama

Look up enum values

pc_get_enums
Read-onlyIdempotent

Retrieve valid enum values for Partner Center API requests before building a request body. Check billingCycle, subscriptionStatus, and more.

Instructions

Return the accepted values for a Partner Center enum, each with a note on what it means — billingCycle, termDuration, targetView, segment, transitionType, subscriptionStatus, qualification, agreementType, billingType, provisioningStatus and more. Use this before sending a request body so you send a value the API will accept, rather than guessing a plausible-looking string. For the fields of a whole resource use pc_get_resource; for a pre-filled body skeleton use pc_build_request. Read-only, offline, deterministic. Omitting name returns the index of every enum instead of one enum's values. An unknown name returns ok:false with suggestions listing all valid enum names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoEnum to expand, e.g. "billingCycle" or "subscriptionStatus". Matched case-insensitively. Omit it to list every available enum with its description and value count, then call again with the one you want.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesTrue when the call succeeded and `data` is populated; false when `error` explains why not.
dataNoThe result payload. Present only when `ok` is true.
errorNoHuman-readable reason the call failed. Present only when `ok` is false.
suggestionsNoValid values to retry with, returned alongside `error` when the requested identifier was not found.
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds meaningful context: 'offline, deterministic', the index returned when name is omitted, and the error shape with suggestions for unknown names. No contradiction with annotations.

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

Conciseness5/5

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

The description is compact and front-loaded, with each sentence serving a distinct purpose: primary function, usage context, sibling alternatives, behavioral notes. No fluff or redundancy.

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

Completeness5/5

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

The tool is simple (one optional parameter) and the description covers all key aspects: what it returns, when to use it, how it behaves with omitted/unknown names, and relationship to siblings. Output schema exists, so return details are already specified.

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

Parameters3/5

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

The input schema description covers 100% of parameter semantics, including examples, case-insensitivity, and the omit behavior. The tool description reiterates these points but adds little beyond the schema; baseline 3 is appropriate.

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 states clearly that the tool returns accepted values for a Partner Center enum with explanations, and lists common enum names. It distinguishes itself from sibling tools by explicitly pointing to pc_get_resource and pc_build_request for different needs.

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?

Provides explicit when-to-use guidance ('Use this before sending a request body... rather than guessing'), names alternatives (pc_get_resource, pc_build_request), and explains behavior for omitted or unknown names. This is strong direction on selecting the correct tool.

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/tunahanaliozturk/partner-center-mcp'

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