Skip to main content

Documentation Index

Fetch the complete documentation index at: https://hypha-docs.plinqx.app/llms.txt

Use this file to discover all available pages before exploring further.

The Playground lets you test tools directly in Plinqx’s interface. Test tools before adding them to production collections, debug issues, and verify configurations.

​
Overview

The Playground provides:
  • Direct Testing: Execute tools without an AI client
  • Real Responses: See actual API responses
  • Context Testing: Test with store and principal context
  • Debugging: Identify configuration issues quickly

​
Testing Modes

The Playground supports two modes:

​
Connection Mode

Test tools directly from a connection (provider, MCP server, etc.):
  • See raw tools as they come from the source
  • No aliases or policies applied
  • Useful for debugging connection issues

​
Collection Mode

Test tools as they appear to AI clients:
  • Aliases applied
  • Policies enforced
  • Store exposure filtering
  • Credential policy evaluation

​
Using the Playground

1

Navigate to Playground

Click Playground in the sidebar.
2

Choose Mode

Select Connection or Collection mode.
3

Select Source

  • Connection Mode: Choose a connection (Salesforce, MCP server, etc.)
  • Collection Mode: Choose a collection
4

Select Tool

Choose a tool from the dropdown.
5

Provide Input

Fill in the tool’s parameters.
6

Execute

Click Execute Tool to run the tool.
7

View Results

See the response in the results panel.

​
Context Testing

In Collection mode, you can test tools with specific contexts:

​
Test as Store

Simulate which tools a specific AI platform would see:
1

Enable Store Context

Toggle Test as Store ON.
2

Select Store

Choose ChatGPT, Claude, or Gemini.
3

View Filtered Tools

Only tools exposed to that store appear in the tool list.

​
Test as Principal

Test credential availability for a specific user:
1

Enable Principal Context

Toggle Test as Principal ON.
2

Select Principal

Choose a user/principal from the dropdown.
3

View Credential Status

Tools show credential status badges:
  • System: Using tenant-level credentials
  • User: Principal has their own credentials
  • No credentials: USER_REQUIRED but principal has no credentials

​
Tool Status Indicators

When testing with context, tools show status badges:
BadgeMeaning
SystemUsing system/tenant credentials
UserPrincipal has user credentials available
No credentialsUSER_REQUIRED but principal lacks credentials
Not exposedTool not exposed to selected store
DisabledTool disabled or unavailable

​
Best Practices

Test Before Publishing

Always test tools in the Playground before adding to production collections

Use Context Testing

Test with store and principal context to verify exposure and credentials

Check Responses

Verify response format matches expectations

Test Edge Cases

Test with various input values to catch errors

​
Troubleshooting

​
Tool Not Appearing

If a tool doesn’t appear:
  • Check if it’s enabled in the collection
  • Verify store exposure settings
  • Ensure the tool is published

​
Execution Errors

If execution fails:
  • Check credential configuration in Vault
  • Verify endpoint URL and parameters
  • Review error message for details

​
Credential Issues

If credential status shows “No credentials”:
  • Verify principal has OAuth connection (for USER_REQUIRED tools)
  • Check Vault entry is valid
  • Ensure credential policy is configured correctly

​
Next Steps

Create Custom Tools

Build and test custom tools

Configure Collections

Add tested tools to collections