Skip to main content
Glama
Sign In
originselect

originselect

by chhavimishra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

search_brands

Find ethical brands by country, values, and category. Get detailed profiles for women-owned, B-Corp, and organic companies including verified origins, websites, and product counts.

Instructions

Search for ethical and origin-verified brands on OriginSelect. Filter by country of origin, ethical values (women-owned, b-corp, organic, etc.), and product category. Returns brand details including values, website, and product count.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_brands"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoCountry of origin to filter by
valuesNoEthical/ownership values to filter by
categoryNoProduct category the brand operates in
brandNoBrand name to look up directly
marketNoMarket scopeall
limitNoMaximum number of brands to return (1-20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.9

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully discloses return values ('brand details including values, website, and product count') compensating for the missing output schema, though it omits safety permissions or error handling specifics.

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 well-structured sentences: purpose declaration, filtering capabilities, and return value disclosure. No redundant or filler text. Information is front-loaded with the core action in the first sentence.

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 the rich input schema (100% coverage, 3 enum fields) and lack of output schema, the description appropriately focuses on explaining the return structure and primary use case. It adequately covers the tool's functionality without needing to document individual parameters that are well-schematized.

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?

Input schema has 100% description coverage, establishing a baseline of 3. The description mentions filter categories (country, values, category) but primarily repeats enum examples already present in the schema without adding syntax guidance, validation rules, or semantic relationships between parameters.

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 the specific action (search), resource (ethical and origin-verified brands), and platform (OriginSelect). It distinguishes from sibling 'search_products' by focusing on brands rather than individual products.

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 implies usage through filter examples (country, values, category) but provides no explicit when-to-use guidance versus siblings like 'refine_search' or 'get_categories/get_values' discovery tools. No prerequisites or exclusions are mentioned.

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