Skip to main content
Glama

Search supplement categories

search_supplements
Read-onlyIdempotent

Search the supplement categories Her Vitals covers for UK women across life stages (trying to conceive, pregnancy, postnatal, perimenopause, menopause, senior). Free-text query matches on the nutrient name, the EFSA-permitted "contributes to normal ..." roles, the "what to look for when buying" points and the named UK brand placeholders. Returns information only, not medical advice; supplements are regulated as food, not medicines. Read-only.

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_supplements"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoFree-text match on name, roles, buying points and brands.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-redundant context: results are information only, not medical advice, and supplements are regulated as food not medicines — a scope/liability boundary an agent should know. It stops short of describing result shape or empty-query behavior.

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?

Front-loaded with the core action and matching fields, then the supporting regulatory caveat. Three sentences with little waste, though the regulatory disclaimer is somewhat verbose relative to the retrieval information conveyed.

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

Completeness3/5

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

For a one-parameter read tool with full annotation coverage this is close to sufficient, but with no output schema the description should give some sense of what a result record contains, and it is silent on the optional-parameter case. Those are real gaps for a search tool.

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% and the schema's own description ("Free-text match on name, roles, buying points and brands") is nearly identical to the description's wording. The description spells out the abbreviations slightly (EFSA-permitted roles, brand placeholders) but adds no format, matching, or ranking semantics 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?

States a specific verb and resource ("Search the supplement categories") plus the exact corpus searched and the fields a query matches against (nutrient name, EFSA roles, buying points, brand placeholders). An agent knows precisely what this tool retrieves without opening the schema. No siblings exist, so no differentiation is needed.

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 by enumerating what a free-text query can match, which helps an agent phrase a query. However, it never addresses the notable fact that `query` is optional (0 required parameters) — what happens with an empty query is left entirely to inference. No when-not guidance or alternative paths are offered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources