Skip to main content
Glama
Sign In

GreenCycle Compound Atlas

by com.greencyclepedia
OverviewDiscussionsAdmin

Get a molecular target

get_target
Read-onlyIdempotent

Use when asked about a receptor, channel or enzyme. One receptor, ion channel or enzyme by name or gene (for example CB1, CNR1, TRPV1, GPR55, FAAH, CYP3A4): what it is, where it sits in the body, the compounds mapped to it with their action, effect and evidence grade, and every measured binding or functional value with species and PubMed identifiers, plus the measured 3D structure (the PDB entry, method, resolution, organism, paper, licence, a viewer link and a still picture) or "No measured structure yet". Educational reference, not medical advice. Example arguments: {"id":"CB1"}.

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": {
      "id": "<id>"
    },
    "name": "get_target"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTarget id, name or gene.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description still adds substantial context beyond them: the full return payload shape, the 'No measured structure yet' fallback sentinel, and the 'Educational reference, not medical advice' framing. With no output schema, carrying the return-value burden is precisely what the description needs to do, and it does it.

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 trigger is front-loaded and the example arguments close it cleanly. The middle is one long run-on sentence with a dense nested parenthetical enumerating structure fields, which is information-rich but harder to scan than a short bulleted breakdown would be.

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?

Single required parameter, no output schema, no nested objects — the description supplies everything an agent needs: when to call it, accepted identifier forms, the complete return contents, the empty-result sentinel, and a usage disclaimer. Nothing material is missing for a tool of this complexity.

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 single parameter is already documented as 'Target id, name or gene,' so baseline is 3. The description earns an extra point by supplying concrete accepted value forms (CB1, CNR1, TRPV1, GPR55, FAAH, CYP3A4) and an example argument object, which clarifies the id-vs-name-vs-gene ambiguity the schema leaves open.

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 and resource ('One receptor, ion channel or enzyme by name or gene') and enumerates exactly what comes back: identity, location, mapped compounds with action/effect/evidence grade, measured binding values with species and PubMed IDs, and 3D structure details. An agent can distinguish this from compound- or structure-oriented siblings without opening the schema.

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?

Opens with an explicit trigger, 'Use when asked about a receptor, channel or enzyme,' which sets the domain clearly. It does not, however, name any alternative or exclusion — for example when to use list_structures_for_target for structure-only queries, or how this differs from search — so routing among siblings is left to inference.

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