Skip to main content
Glama

CovaSyn Chemistry Tools

covabasic_druglikeness

Evaluate drug-likeness: Lipinski Ro5, Veber, Ghose, Egan, Muegge, Ro3 (fragments), QED score, synthetic accessibility (SA) score.

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": {
      "smiles": "<smiles>"
    },
    "name": "covabasic_druglikeness"
  }
}

Input Schema

NameRequiredDescriptionDefault
smilesYes
api_keyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the behavioral scope by listing every check performed, which is useful, but says nothing about error handling for invalid SMILES, the role/requirement of the api_key, or whether the evaluation is a pure static computation versus a remote call. Output schema existence reduces the need to describe return values.

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 sentence front-loads the verb and then enumerates the returned analyses. Nothing is redundant and there is no filler, though the parenthetical abbreviations are terse enough to require domain familiarity.

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

Completeness3/5

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

Because an output schema exists, return values need not be explained, and the description does fully enumerate what is evaluated. However, for a tool with two parameters at 0% schema coverage and no annotations, it leaves the input format and api_key semantics unexplained and does not distinguish itself from the covachem_druglikeness sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and both parameters (smiles, api_key) are undocumented in the schema. The description does not compensate: it never states that input is a SMILES string, nor what api_key is for or whether it is needed. Only an inference from the domain hints at the input format.

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?

States a specific verb+resource ('Evaluate drug-likeness') and enumerates exactly which rulesets and scores are computed (Lipinski Ro5, Veber, Ghose, Egan, Muegge, Ro3, QED, SA), so the agent knows precisely what analysis is performed. It does not differentiate itself from the near-identical sibling covachem_druglikeness, leaving ambiguity about which to call.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The presence of covachem_druglikeness and covabasic_filter_check as plausible substitutes makes the absence of routing guidance a real gap.

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.