MyPlayground
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_level_mappingA | REQUIRED: Call this tool FIRST to find the company's specific level names (e.g., '63', 'L5', 'E4') versus the industry 'Standard' ladder. 'role' must be the full name: 'Software Engineer', 'Product Manager', etc. |
| get_recent_offersB | Fetch the most recent specific salary offers for a given role to gauge current market trends. Example: company_name='Amazon', role='Software Engineer', level='SDE II' Location must be a single city name (e.g., 'Seattle'). If the city is ambiguous, the most major tech hub will be chosen by default |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one maps company-specific levels to standard ladders, the other fetches recent salary offers. No overlap in functionality.
Both tools use a consistent verb_noun pattern in snake_case: get_level_mapping and get_recent_offers, following the same style.
With only 2 tools, the server feels underdeveloped for its likely domain (compensation research). More tools like search by company or role would be expected, but the set is not extreme.
The surface covers level mapping and recent offers but lacks tools for discovering companies, roles, or historical salary trends. Some standard operations are missing, but core use cases are addressed.