Prycd Pricing MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API 密钥 |
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 |
|---|---|
| pricepropertyC | Returns PRYCD estimated value for requested property |
| healthcheckA | Returns your input back to you to verify that the API is up and your API key is valid. |
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 checks API health, the other retrieves property pricing. There is no ambiguity.
Both tool names are single compound words in lowercase (healthcheck, priceproperty). While not following a strict verb_noun pattern, they are consistently formatted.
With only 2 tools for a pricing server, the surface is too thin. A pricing service typically requires multiple operations beyond a single value lookup.
The server only offers a health check and a single pricing lookup. Missing are tools for searching properties, comparing values, or handling batch requests, leaving significant gaps.