AgentShare — Solana DeFi Intelligence MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X-API-Key | No | API key for authentication with the AgentShare service, used in REST API requests (as X-API-Key header) or MCP (in Authorization: Bearer header). Obtain from https://agentshare.dev/pricing. | |
| Authorization | No | Bearer token for authentication with the AgentShare service, used in MCP (as Authorization: Bearer header) or REST API. Should include the API key prefixed with 'Bearer '. Obtain from https://agentshare.dev/pricing. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| price_searchA | Search connected marketplaces and return structured offers (prices, sources, freshness). Use when the user wants to compare options, browse multiple listings, or explore a product category or model—not when they only need one definitive 'cheapest' pick (use best_offer). Accepts free-text queries in any language. |
| best_offerA | Return the single best current offer for a product intent: typically lowest price among in-stock listings the API trusts. Use when the user asks where to buy something cheapest, 'best deal', or one clear recommendation. For side‑by‑side comparison of many listings, prefer price_search. |
| best_offer_under_budgetA | Find the best offer for a product query with a maximum price ceiling. Use when the user gives a budget, 'under $X', 'below …', or 'no more than …'. Pass max_price in the same numeric unit the deployed API expects for that field (see API docs). Do not use for open-ended comparison without a cap—use price_search or best_offer. |
| service_metaA | Return API capabilities, rate limits, and integration hints. Safe to call without an API key when the deployment allows it. Use for onboarding, capability checks, or answering 'what can this API do?' before calling paid tools. |
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 4 tools
Each tool has a clearly distinct purpose: best_offer for single cheapest offer, best_offer_under_budget for budget-constrained offers, price_search for multi-offer comparison, and service_meta for API metadata. The descriptions explicitly differentiate when to use each tool, with no functional overlap.
All tools follow a consistent snake_case naming pattern with clear verb-noun combinations (best_offer, price_search, service_meta). The naming is predictable and follows the same stylistic convention throughout.
Four tools is perfectly appropriate for a price API server - it covers the core use cases (single offer, budget-constrained offer, multi-offer search, and service metadata) without being overly sparse or bloated. Each tool earns its place in the set.
The toolset covers the essential price comparison workflows well, with clear guidance on when to use each tool. The only minor gap is the lack of tools for more advanced operations like price tracking, historical price data, or alerting, but the core functionality is complete for basic price queries.