Skip to main content
Glama

CovaSyn Chemistry Tools

covachem_druglikeness

Evaluate drug-likeness filters (Lipinski, Ghose, Veber, PAINS, etc.).

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

Input Schema

NameRequiredDescriptionDefault
smilesYes
api_keyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/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 says nothing about which filters are actually returned, whether the evaluation is read-only, whether api_key authentication is required, or how results are structured. The vague trailing "etc." leaves the filter set undefined.

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 front-loaded sentence with no wasted words, naming the operation and giving illustrative filter examples. Appropriately sized, though slightly under-specified rather than truly concise.

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?

An output schema exists, so return values need not be described. But for a compute tool with zero annotations and undocumented parameters, the description omits whether filter selection is configurable and leaves both inputs unexplained, making it minimally adequate at best.

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% for two parameters, and the description adds no meaning for either. It neither explains the SMILES input format nor what api_key is for, so it fails to compensate for the coverage gap.

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 ("Evaluate") and resource ("drug-likeness filters") and enumerates concrete filter names (Lipinski, Ghose, Veber, PAINS), so the agent knows exactly what the tool computes. However, it does not distinguish itself from the near-identically named sibling covabasic_druglikeness, so an agent cannot tell why it should pick one over the other.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. With siblings like covabasic_druglikeness, covabasic_filter_check, and covabasic_reynolds all plausibly overlapping, the absence of routing guidance is 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.