Skip to main content
Glama

HealthStylz Clinical Nutrition & Circadian Environment MCP

search_healthstylz_articles

Search 1,126+ registered dietitian and evidence-grounded health, recipes, nutrition, movement, and wellness articles.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "search_healthstylz_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch terms (e.g. salmon, resistance training, sleep hygiene, fiber)
limitNoMaximum articles to return (1-20, default 5)
topicNoOptional topic filter: recipes, fitness, weight, supplements, aging, family, mind, drinks, decor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no ranking/relevance behavior, whether search is keyword or semantic, no note on empty results or pagination. Only the corpus size (1,126+) is offered, which is a marketing detail rather than operational 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?

A single front-loaded sentence with no filler, though the '1,126+' figure spends words on trivia rather than search behavior. It is efficiently sized for a simple search tool.

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

Completeness2/5

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

For a tool with zero annotations and no output schema, the description should at least hint at return shape (titles, snippets, URLs) and search semantics; it does neither. What an agent gets back and how ranking works is completely unspecified.

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 coverage is 100% including example terms and the allowed range/default for limit and the topic filter list, so the schema already does the work. The description adds no parameter-level meaning beyond what is structured, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: 'Search ... health, recipes, nutrition, movement, and wellness articles' in a dietitian-grounded corpus. It's clearly distinct from siblings like lookup_supplement_evidence or get_daily_wellness_brief, though the description never names those alternatives explicitly.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance; nothing tells the agent when to prefer this over lookup_supplement_evidence or get_herb_guides. The domain list implies article retrieval but the routing decision is left entirely to inference.

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.