Skip to main content
Glama
ABAKHAR721

Product Data Tools MCP Server

by ABAKHAR721

query_store_products

Retrieve product data from a specified store with optional filters, sorting, and field selection to find matching products.

Instructions

Retrieves product data from a specific store based on filtering and sorting criteria.

Uses a separate Product Data Server to fetch information.

Args: store_name: The name of the store to search within (e.g., 'aeropress_product_cleaned'). This is required. filter_criteria: Optional. A dictionary specifying filter criteria. Keys are field names (e.g., 'price', 'rating'). Values are either exact match values (e.g., {'rating': 4.5}) or dictionaries for operators (e.g., {'price': {'operator': '<', 'value': 50.0}}). Supported operators by the data server include '==', '!=', '<', '>', '<=', '>='. Consult data server documentation (or the available_fields tool) for available fields and operators. sort_by: Optional. The field name to sort the results by (e.g., 'price', 'rating', 'score'). If not specified, the data server might default to 'score' or its own internal default. sort_order: Optional. The order of sorting ('asc' for ascending, 'desc' for descending). Defaults to 'desc'. limit: Optional. The maximum number of products to return. Defaults to 10. fields: Optional. A list of specific fields to include in the results (e.g., ['product_name', 'price', 'product_url']). If not specified, the data server returns all available fields for the matching products.

Returns: A list of product dictionaries matching the criteria on success. Returns a string error message if the data server cannot be reached, the store is not found, or if there's an error during the query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_nameYes
filter_criteriaNo
sort_byNo
sort_orderNodesc
limitNo
fieldsNo
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses behavioral traits such as error conditions (server unreachable, store not found, query error) and defaults (sort_by may default to 'score', limit defaults to 10). This provides good transparency for a read operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately long but well-structured with Args and Returns sections. It could be slightly more concise (e.g., 'Optional.' repeats), but every sentence contributes useful information. It is front-loaded with the core action.

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?

Given 6 parameters, one required, no output schema, and sibling tools for additional context, the description covers parameter semantics, default behaviors, and error returns. It could be more specific about output field structure, but the mention of 'product dictionaries' is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate fully. It does so with an Args section explaining each parameter's purpose, defaults, and value format (e.g., filter_criteria operators, fields list behavior). This adds significant meaning beyond the schema.

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 retrieves product data from a specific store with filtering and sorting. It distinguishes itself from siblings (store-specific vs. global top products or URL-based details). Verb 'retrieves' and resource 'product data from a specific store' are specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives like get_overall_top_products or get_product_details_by_url. Usage is implied through parameter descriptions, but no when-not-to-use guidance is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ABAKHAR721/data_mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server