Skip to main content
Glama
Sign In
AgentShare — Solana DeFi Intelligence MCP

AgentShare — Solana DeFi Intelligence MCP

by anhmtk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search product listings

price_search
Read-onlyIdempotent

Search multiple marketplaces to compare product prices, sources, and freshness for informed purchasing decisions.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "price_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesKeywords: product name, model number, brand, or category.
limitNoMaximum rows to return (higher = broader scan, more tokens).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate this is a read-only, idempotent, open-world operation. The description adds valuable behavioral context about multilingual support ('free-text queries in any language') and the nature of returned data (structured offers with freshness indicators), though it doesn't mention rate limits or authentication requirements.

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 efficiently structured in two sentences: the first states the core functionality and return format, the second provides usage guidelines and parameter context. Every phrase adds value with zero redundancy.

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

Completeness4/5

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

For a read-only search tool with comprehensive annotations and full schema coverage, the description provides excellent purpose clarity and usage guidelines. The main gap is the lack of output schema, but the description adequately describes the return format (structured offers with prices, sources, freshness).

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?

With 100% schema description coverage, the schema already fully documents both parameters. The description adds minimal semantic context beyond the schema, mentioning 'free-text queries in any language' which slightly elaborates on the query parameter's flexibility.

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 clearly states the tool searches marketplaces and returns structured offers with specific attributes (prices, sources, freshness). It explicitly distinguishes from sibling 'best_offer' by stating this is for comparison/browsing rather than finding a single definitive cheapest pick.

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?

The description provides explicit guidance on when to use this tool ('when the user wants to compare options, browse multiple listings, or explore a product category or model') and when not to use it ('not when they only need one definitive cheapest pick'), with a named alternative ('use best_offer').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools