Skip to main content
Glama

Biomarkers a supplement affects

get_biomarkers_for_supplement
Read-onlyIdempotent

Biomarkers a supplement moves in the Aviado app's evidence graph, one entry per biomarker (strongest edge), ordered by prior_weight (graph evidence weight 0-1, not a calibrated probability or effect size). Each entry has direction (up/down/bidirectional), goal/subgoal, has_verified_support / mixed_evidence, up to 3 PubMed IDs (pmids; URL template in coverage) with n_studies / rct_count, and dose (mean study dose {value, unit}: evidence context, not a dosing recommendation; see coverage.dose_note); null fields are omitted. Partial and non-exhaustive: a missing biomarker is not evidence of no effect. The supplement may be a name or an Aviado canonical_id (from search_supplements or a candidates list). Check status first: needs_confirmation / no_match means the input did not resolve, data is null and next_step says how to retry.

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": {
      "supplement": "<supplement>"
    },
    "name": "get_biomarkers_for_supplement"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 25, max 100)
supplementYesSupplement name (e.g., 'fish oil', 'curcumin', 'vitamin D3')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / supplement / maxLength
      Added value: +512
    • addedInput schema / properties / supplement / minLength
      Added value: +1
  2. Changed1 schema field changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 25,
      +  "description": "Max results (default 25, max 100)",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds a lot beyond them: ordering by prior_weight with the explicit caveat that it is graph evidence weight, not a calibrated probability or effect size; that dose is evidence context and not a dosing recommendation; that null fields are omitted; and that results are partial/non-exhaustive so absence is not evidence of no effect. These are exactly the non-obvious traits an agent needs.

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 dense paragraph with no filler sentences, and it front-loads the core purpose before the field-by-field detail and the status-handling note. The heavy parenthetical nesting makes it harder to scan than it needs to be, but nothing is wasted.

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

Completeness5/5

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

There is no output schema, so the description carries the full burden of explaining return shape, and it does: per-entry fields (direction, goal/subgoal, verification flags, pmids with n_studies/rct_count, dose), omission of nulls, ordering, and failure states. An agent can interpret a response without further documentation.

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%, so the baseline is 3, but the description adds meaning the schema lacks: the supplement parameter accepts either a plain name or an Aviado canonical_id, and where to obtain one. The limit parameter is left to the schema, which documents it fully.

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+resource and direction: 'Biomarkers a supplement moves in the Aviado app's evidence graph, one entry per biomarker (strongest edge).' This is unambiguously the supplement→biomarker direction, distinct from the inverse sibling get_supplements_for_biomarker and from the broader get_interventions_for_biomarker.

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 real invocation guidance: the supplement argument may be a name or canonical_id sourced from search_supplements/candidates, and it instructs the agent to 'check status first' with named status values (needs_confirmation/no_match) and what to do on failure. It stops short of naming an alternative tool or an explicit when-not-to-use condition, so it is clear context rather than full routing.

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