CovaSyn Chemistry Tools

covasyn_jobs

List your async GPU jobs — running, finished and failed.

Parameters:
  scope: "canvas" (default) for jobs started from the current canvas,
         or "account" for every job on your account.
  tool:  optional filter, e.g. "covafold". Empty (default) returns EVERY
         durable job — an LLM asked "what jobs do I have?" must not be
         handed a silently truncated answer. A UI that can only act on one
         kind of job passes its own filter explicitly.

Returns: {jobs: [{job_id, tool, state, submitted_at, credits, importable}]}.
FREE — never costs credits. Never returns sequences or structures; fetch
those with covasyn_job_detail / covasyn_job_result.

Input Schema

Name	Required	Default
`tool`	No
`scope`	No	canvas
`api_key`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does it well: it declares the tool is FREE and never costs credits, warns that sequences/structures are never returned, and highlights that an empty tool filter deliberately returns every durable job to avoid silent truncation. Missing only auth/permission notes for the api_key parameter.

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?

Front-loaded purpose line, then a parameter block and a returns block, which makes it easy to scan. The parenthetical about an LLM asking "what jobs do I have?" is a slightly chatty justification but earns its place by explaining the default.

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 zero-required-param listing tool with an output schema, this is close to complete: parameters, defaults, cost, and sibling routing are all covered. The only redundancy is restating the return shape that the output schema already provides, and the omitted api_key semantics.

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 description coverage is 0%, so the description must compensate, and it documents scope and tool in detail, including defaults and the anti-truncation rationale. It adds meaning well beyond the bare typed fields, though api_key is unaddressed.

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 ("List your async GPU jobs") and enumerates the states covered (running, finished, failed). It also names the sibling tools (covasyn_job_detail / covasyn_job_result) that carry the data this tool deliberately omits, so an agent can separate it from adjacent job tools.

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?

Explains the semantics of the scope filter (canvas vs account) and the tool filter, including the intent behind the empty default (don't silently truncate). It routes the agent to covasyn_job_detail / covasyn_job_result for sequences and structures, though it never states an explicit when-not-to-use case.

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

All CovaSyn Chemistry Tools tools Inspect

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.