Skip to main content
Glama
Sign In

Remy Research MCP

by com.remyresearch
OverviewDiscussionsAdmin

search_products

Read-onlyIdempotent

Search public product variants by query, compound, format, brand, inStockOnly and inclusive single-unit AED price bounds. Results rank exact matches first and include strength, volume, storage guidance and batch-report evidence with unknowns explicit. For Research Use Only. This research-use-only catalogue is for buyers 21+ years of age and is supplied for research purposes only. Not for human or veterinary use. Return exact id values to the basket tools; sku, name and URL are not basket IDs. No personal information required.

Input Schema

NameRequiredDescriptionDefault
brandNoExact catalogue brand name, case-insensitive, e.g. ProPeptide.
limitNoMaximum products returned, 1–50. Default 20.
queryNoOptional product text or compound alias. Exact IDs/names rank first. Never include personal information.
formatNoProduct format. vial includes vial kits; kit amounts remain explicit in strength.label.
offsetNoStart at 0 or use nextOffset. Keep filters unchanged across pages.
compoundNoExact compound name, ID or documented alias, e.g. BPC-157 or bpc157. Includes blends containing that compound.
inStockOnlyNoReturn only currently orderable, in-stock variants. Defaults to false.
maxPriceAedNoInclusive maximum single-unit AED price, before discounts/delivery.
minPriceAedNoInclusive minimum single-unit AED price, before discounts/delivery.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / brand
      Added value: +{
+  "description": "Exact catalogue brand name, case-insensitive, e.g. ProPeptide.",
+  "maxLength": 80,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / compound
      Added value: +{
+  "description": "Exact compound name, ID or documented alias, e.g. BPC-157 or bpc157. Includes blends containing that compound.",
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / format
      Added value: +{
+  "description": "Product format. vial includes vial kits; kit amounts remain explicit in strength.label.",
+  "enum": [
+    "vial",
+    "pen"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / inStockOnly
      Added value: +{
+  "description": "Return only currently orderable, in-stock variants. Defaults to false.",
+  "type": "boolean"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum products to return, as a JSON integer from 1 to 50."New value: +"Maximum products returned, 1–50. Default 20."
    • addedInput schema / properties / maxPriceAed
      Added value: +{
+  "description": "Inclusive maximum single-unit AED price, before discounts/delivery.",
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / minPriceAed
      Added value: +{
+  "description": "Inclusive minimum single-unit AED price, before discounts/delivery.",
+  "minimum": 0,
+  "type": "number"
+}
    • changedInput schema / properties / offset / description
      Previous value: -"Pagination offset. Start at 0 or use nextOffset from the previous search result."New value: +"Start at 0 or use nextOffset. Keep filters unchanged across pages."
    • changedInput schema / properties / query / description
      Previous value: -"Optional product search text, up to 120 characters. Omit to browse; never include personal information."New value: +"Optional product text or compound alias. Exact IDs/names rank first. Never include personal information."
  2. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum products to return, as a JSON integer from 1 to 50."
    • addedInput schema / properties / offset / description
      Added value: +"Pagination offset. Start at 0 or use nextOffset from the previous search result."
    • addedInput schema / properties / query / description
      Added value: +"Optional product search text, up to 120 characters. Omit to browse; never include personal information."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuine behavioral detail beyond that: results rank exact matches first and include strength, volume, storage guidance and batch-report evidence with unknowns made explicit. The RUO/21+ notices are policy context rather than operational behavior, which keeps this short of a 5.

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

Conciseness3/5

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

The purpose and result behavior are front-loaded well, but the legal block is redundant, restating research-use-only three times ('For Research Use Only', 'research-use-only catalogue... supplied for research purposes only', 'Not for human or veterinary use'). That padding dilutes an otherwise tight description.

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 no output schema, the description usefully covers what comes back (ranked results, strength, volume, storage, batch evidence), how ids should be reused, and policy constraints. Pagination semantics for limit/offset exist only in the schema, but with 100% coverage that gap is minor.

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?

Schema description coverage is 100%, so every parameter is already documented with types, bounds and formats; the description's parameter list largely restates that. It adds no new syntax or interaction rules (e.g. how price bounds combine with inStockOnly) beyond what the schema gives, so the baseline 3 applies.

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?

States a specific verb and resource ('Search public product variants') and enumerates the exact filter dimensions it accepts. It also disambiguates from the sibling basket tools by stating that only exact id values feed the basket tools, so an agent can place it in the workflow without opening a schema.

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?

Gives clear context for use (catalogue search whose exact ids are the input to basket tools) and a concrete negative rule ('sku, name and URL are not basket IDs'). It does not specify when an agent should prefer compound vs query vs brand filters, so guidance is contextual rather than prescriptive.

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

All Remy Research MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources