Skip to main content
Glama

agenticfeed

by io.github.bluestratus

search_products

Find a merchant's products that match a shopper's need, question, problem, or use case. Pass the buyer intent in natural language (e.g. "a light strategy game for 4 players under thirty pounds"); returns ranked in-stock products with the reason each fits, drawn from Agenticfeed's intent mapping (questions, problems, use cases). Call find_merchant first to get the merchant ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return (default 5, max 10).
queryYesThe shopper's need, in natural language.
merchantYesAgenticfeed merchant ID (customer GUID).

TDQS

A4.4/5.0
Behavior4/5

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

No annotations present, so description carries full burden. Discloses that results are ranked, in-stock, and include reasons from intent mapping. Does not mention error or permission details, but sufficient for a search tool.

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?

Three precise sentences: purpose, functionality + example, prerequisite. No fluff, front-loaded with key 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?

With 3 params and no output schema or annotations, description explains usage, return value (ranked in-stock products with reasons), and prerequisite. Adequately complete for a search tool.

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

Parameters4/5

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

Schema coverage is 100% (baseline 3). Description adds example query and explains merchant parameter via prerequisite (find_merchant), providing value beyond 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?

Description clearly states verb (Find), resource (merchant's products), and context (matching shopper's need). Distinguishes from siblings: find_merchant (ID retrieval), get_product (specific product), list_products (unranked listing).

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

Usage Guidelines4/5

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

Explicitly says to call find_merchant first to get merchant ID, and to pass buyer intent in natural language. Implicitly suggests not to use for browsing (sibling list_products). Could be more explicit about when-not-to-use, but overall clear.

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

All agenticfeed toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose: find_merchant resolves merchant identity, get_product fetches product details, list_products enumerates products, and search_products finds products by intent. No overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores (find_merchant, get_product, list_products, search_products), making them predictable and easy to understand.

Tool Count5/5

With 4 tools covering merchant discovery, product listing, detail retrieval, and intent-based search, the count is well-scoped for a product feed server and neither too few nor too many.

Completeness4/5

The set covers key read operations for a product feed, but lacks tools for browsing merchants without a prior domain or for updating/deleting products, which are minor gaps given the intended scope.

Resources