Skip to main content
Glama
Sign In

GreenCycle Compound Atlas

by com.greencyclepedia
OverviewDiscussionsAdmin

Find the studies behind a finding

find_studies
Read-onlyIdempotent

Use when asked "what is the evidence" or "which studies". The PubMed studies Greencyclepedia cites for a compound, a target, a condition or a compound at one target, each with its PubMed link, what it supports (an effect at a target, a binding value, a caution, a systematic review or a trial as administered) and the Greencyclepedia record it belongs to, plus the PubMed search behind each record. Doses are left out on purpose. Educational reference, not medical advice. Example arguments: {"compound":"cbd","condition":"epilepsy"}.

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": "find_studies"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many items to return, at most 50.
queryNoOr a plain phrase, for example "cbd epilepsy" or "studies on CB1": the compound, target and condition it names are used.
targetNoA target, for example "TRPV1".
compoundNoA compound id or name, for example "cbd".
conditionNoA condition, for example "epilepsy".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Or a plain phrase, for example \"cbd epilepsy\" or \"studies on CB1\": the compound, target and condition it names are used.",
+  "maxLength": 120,
+  "type": "string"
+}
  2. First observed

TDQS

A3.9/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 safety is covered. The description adds real value beyond that by disclosing the per-item return contents (PubMed link, what the study supports, the owning Greencyclepedia record, the underlying PubMed search), the deliberate omission of doses, and an 'educational reference, not medical advice' caveat.

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?

The usage trigger is correctly front-loaded and there is no filler or marketing language. The second sentence is an overlong run-on enumerating return fields, which slightly hurts scannability compared with a short list.

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?

For a read-only lookup with no output schema, the description covers purpose, triggering questions, item contents, an intentional exclusion (doses), and a usage disclaimer. The main remaining gap is guidance on combining or prioritizing the five optional filters and on what an empty result means.

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%, so the schema already explains each of the five optional filters including the free-text `query` and the `limit` cap. The description only adds the combined-filter idea ('a compound at one target') and one example argument object, which is a marginal increment over structured data.

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?

The description states a concrete verb and resource: it returns the PubMed studies Greencyclepedia cites for a compound, target, condition, or a compound-at-target pair. The scope is narrowed ('studies Greencyclepedia cites') which separates it from a generic web search, but it never names a sibling (e.g. `search` or `list_trials`) that an agent might confuse it with.

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?

The opening trigger phrase is explicit: 'Use when asked "what is the evidence" or "which studies".' That gives a clear when-to-use condition. It offers no exclusion or alternative-tool guidance, so an agent must still decide on its own when `search` or `list_trials` is the better call.

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

All GreenCycle Compound Atlas toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources