Skip to main content
Glama

CovaSyn Chemistry Tools

covasyn_job_detail

Show one job's inputs — the sequence it was given, and its timings.

Parameters:
  job_id: The id from covasyn_jobs, e.g. "covafold-fold_protein:abc123".

Returns: {job: {...}} or {error}. FREE — never costs credits.

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": {
      "job_id": "<job_id>"
    },
    "name": "covasyn_job_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
api_keyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 a meaningful behavioral trait — 'FREE — never costs credits' — and 'Show' implies read-only, plus it gives the return shape ({job} or {error}). It does not mention authentication needs (the api_key parameter) or any rate limits, so the disclosure is partial.

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?

Short and front-loaded: the purpose sentence comes first, followed by a labeled parameter note, return shape, and cost note. Each line adds something; the returns line is mildly redundant given an output schema exists but is not wasteful.

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 simple single-job lookup with an output schema present, the description covers purpose, the key parameter's format, return shape, and cost. The one real gap is the unexplained api_key parameter, which an agent would otherwise have to infer.

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

Parameters3/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. It does a good job on job_id, clarifying the source and giving a concrete format example ('covafold-fold_protein:abc123'), but it never mentions the api_key parameter at all, leaving one of two parameters undocumented everywhere.

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 and resource: 'Show one job's inputs — the sequence it was given, and its timings.' This scopes it to a single job's inputs/timings, which implicitly contrasts with the list-style covasyn_jobs and the result-returning covasyn_job_result. It stops short of naming those siblings explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

There is no explicit when-to-use or when-not-to-use statement. However, 'The id from covasyn_jobs' implicitly routes the agent: call covasyn_jobs first, then this tool. That implied workflow is useful but leaves the choice between this and covasyn_job_result to inference.

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.