Skip to main content
Glama
Sign In

GreenCycle Compound Atlas

by com.greencyclepedia
OverviewDiscussionsAdmin

Cite a Greencyclepedia record

cite
Read-onlyIdempotent

Use when you are about to quote or link Greencyclepedia and need the citation. A ready citation for one Greencyclepedia record (compound, target or condition) or for Greencyclepedia as a whole: the canonical url, the citation line, a BibTeX entry, the version, the original papers to cite for its findings (PubMed links) and the licence (CC BY 4.0 with attribution). Example arguments: {"id":"compound:cbd"}.

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

Input Schema

NameRequiredDescriptionDefault
idNoA record id or name, for example "compound:cbd", "CB1" or "epilepsy". Leave out to cite Greencyclepedia.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"A record id or name, for example \"compound:cbd\", \"CB1\" or \"epilepsy\". Leave out to cite the atlas."New value: +"A record id or name, for example \"compound:cbd\", \"CB1\" or \"epilepsy\". Leave out to cite Greencyclepedia."
  2. First observed

TDQS

A4.5/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 useful behavioral context beyond that: the output includes attribution requirements (CC BY 4.0), versioning, and the original PubMed papers that must be cited for findings — obligations an agent needs to act on correctly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences plus a one-line example: the usage trigger comes first, the returned contents second, and the example last. Every clause carries information; nothing is padding.

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 values, and it does so item by item (url, citation line, BibTeX, version, papers, licence). For a single optional-parameter read tool with annotations covering safety, nothing an agent needs in order to call it or interpret the result 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% and the schema already explains id (record id or name, omit to cite the whole site), so the baseline is 3. The description adds the record-type taxonomy (compound, target or condition) and a concrete example argument, which helps the agent format a valid call.

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?

The description names a concrete verb and resource — producing a ready citation for a single Greencyclepedia record or the site as a whole — and enumerates the payload (canonical url, citation line, BibTeX, version, source papers, licence). It is clearly distinguishable from data-retrieval siblings like get_compound or fetch, since the goal is a quotable citation rather than the record itself.

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?

It gives an explicit trigger: use when you are about to quote or link Greencyclepedia. That is a strong when-to-use signal, and the id-optional framing clarifies the two modes of use. It does not name alternative tools or exclusion cases, which keeps it below a 5.

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