Skip to main content
Glama

Find the evidence on a substance or a question

find_evidence
Read-onlyIdempotent

Answers "what does X do?" and "does X affect Y?" for a supplement, nutrient, drug, food compound or plant (for example "does magnesium help sleep?", "what is creatine shown to do?", "omega-3 and triglycerides"). Pass the substance as query and the effect or outcome asked about, if there is one, as about. When the person names two substances ("is creatine safe with caffeine"), pass one as query and the other as about, in one call; findings about the pair together come back under in_combination. It resolves the name to the node that has findings and returns up to limit findings (default 10), strongest evidence first, each with its evidence strength in words, the study design, the quote, the paper, a permalink and a citation to quote as it stands. total_findings counts every match. The result is complete for the query: another wording of the same substance resolves to the same node, so do not call again to rephrase. Call again only to narrow (evidence_strength, about), to raise limit (at most 50), or to ask about something else. Without about, summary lists everything the node has findings about. If matched is null, or total_findings is 0, Catalyst has recorded no findings on it. That is a complete answer: say so, and do not answer from memory as though from Catalyst. Try search_nodes only when other_matches or summary shows a node the person plausibly meant. An evidence strength says how well the evidence supports a finding and is not a recommendation. For what a compound can become, use reach; for reference-database relations, use get_relations.

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": {
      "query": "<query>"
    },
    "name": "find_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
aboutNoOptional: the effect, outcome or second substance asked about (e.g. "sleep", "blood pressure", "caffeine"), or a node id from search_nodes.
limitNoFindings to return, strongest evidence first. The default is enough to answer; total_findings says how many match.
queryYesThe substance the person asked about, in their words (e.g. "magnesium", "vitamin D", "BPC-157"), or a node id from search_nodes. For a question about an outcome alone (e.g. "what lowers blood pressure"), the outcome.
detailNobrief (default) returns each finding with its claim, evidence strength, design, population, dose, quote, paper, permalink and a citation to quote as it stands. full adds every other recorded field and is longer; use it only when the person asks for all fields.brief
evidence_strengthNoOptional floor: only findings at this evidence strength or stronger, from strong down to insufficient.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / about / description
      Previous value: -"Optional: the specific effect or outcome asked about (e.g. \"sleep\", \"blood pressure\"), or a node id."New value: +"Optional: the effect, outcome or second substance asked about (e.g. \"sleep\", \"blood pressure\", \"caffeine\"), or a node id from search_nodes."
    • changedInput schema / properties / detail / description
      Previous value: -"brief (default): each finding with its claim, evidence strength, design, population, dose, quote, paper, permalink and a ready-to-quote citation. full: every recorded field."New value: +"brief (default) returns each finding with its claim, evidence strength, design, population, dose, quote, paper, permalink and a citation to quote as it stands. full adds every other recorded field and is longer; use it only when the person asks for all fields."
    • changedInput schema / properties / evidence_strength / description
      Previous value: -"Optional floor: only findings with at least this evidence strength."New value: +"Optional floor: only findings at this evidence strength or stronger, from strong down to insufficient."
    • changedInput schema / properties / limit / description
      Previous value: -"Findings to return, strongest evidence first."New value: +"Findings to return, strongest evidence first. The default is enough to answer; total_findings says how many match."
    • changedInput schema / properties / query / description
      Previous value: -"The substance or outcome the person asked about, in their words (e.g. \"magnesium\", \"vitamin D\", \"sleep\"), or a node id."New value: +"The substance the person asked about, in their words (e.g. \"magnesium\", \"vitamin D\", \"BPC-157\"), or a node id from search_nodes. For a question about an outcome alone (e.g. \"what lowers blood pressure\"), the outcome."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only and idempotency, and the description adds substantial context beyond them: name resolution to a node, default limit of 10, strongest-first ordering, fields returned, the meaning of total_findings, and that a null match or zero total is a complete negative answer that must not be replaced with model memory.

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 answerable question shapes and tightly written per sentence, but it is a single dense block that mixes output behavior, negative-result handling and sibling routing without visual structure. Almost every sentence earns its place, though the result-field enumeration is slightly overlong.

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?

For a five-parameter tool with no output schema, it covers the returned fields, ordering, default and ceiling limits, negative-result semantics, idempotency of wording, and when to escalate to sibling tools. Nothing an agent needs in order to call it correctly is missing.

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; the description earns a bump by explaining the non-obvious two-substance pattern (one as query, one as about, pair findings under in_combination) and the evidence_strength-as-floor semantics. It adds less on limit and detail, which the schema already documents.

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?

Names the exact questions it answers ("what does X do?", "does X affect Y?") and the resource domain (supplement, nutrient, drug, food compound, plant), with concrete examples. It also separates itself from search_nodes, reach and get_relations by naming them.

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

Usage Guidelines5/5

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

Explicitly states when to make one call with two substances, when NOT to call again (rephrasing), and the only valid reasons to call again (narrow by evidence_strength/about, raise limit, different substance). It also hands off to search_nodes, reach and get_relations under stated conditions.

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.