CovaSyn Chemistry Tools

covasyn_credits

Show your current credit balance, tier, and pre-paid pack pricing.

Returns:
  - balance: subscription credits remaining (resets weekly to weekly_allocation, capped at max_balance)
  - prepaid_balance: pre-paid credits remaining (no expiration; consumed after sub balance is empty)
  - total_available: balance + prepaid_balance (the actual amount you can spend right now)
  - weekly_allocation: sub credits added every 7 days
  - max_balance: rollover ceiling for sub credits (4× weekly_allocation)
  - tier: free / pro / unlimited / enterprise
  - max_concurrent_calls: parallel call limit for your tier
  - next_reset_at: ISO timestamp when next weekly grant happens
  - pricing_version: currently active pricing version
  - prepaid_packs: list of available credit-pack sizes + EUR prices for your tier

This tool is FREE in all tiers — never costs credits to check your balance.

Input Schema

Name	Required	Description	Default
`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.2/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and delivers: subscription resets weekly and is capped at max_balance, prepaid credits never expire and are consumed only after the subscription balance empties, rollover ceiling is 4× weekly_allocation, and the call itself is free in all tiers. That is precisely the behavioral context an agent needs.

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 with the purpose sentence, then a clean bulleted field list, closing with the free-of-charge note. Every line is informative, though the field-by-field breakdown overlaps with the existing output schema, making it slightly longer than strictly necessary.

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?

For a read-only balance lookup with one auth parameter and an output schema, the description covers everything an agent needs: what it returns, how balances behave, tier limits, and that invoking it costs nothing. No ambiguity remains about calling it.

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% and the single parameter is api_key. The description never mentions the parameter, but an api_key is self-evident authentication and is likely injected globally, so the omission is minor. It adds no semantics beyond the parameter name itself.

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 ('Show') and resource ('your current credit balance, tier, and pre-paid pack pricing'), which is unmistakably distinct from every sibling (job management, analyzers, predictors). An agent reading only the first line knows exactly what this tool is for.

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?

It signals that the tool is safe to call ('FREE in all tiers — never costs credits'), which implicitly encourages its use, but it never states when to call it relative to alternatives (e.g., 'call before submitting a job to verify you can afford it'). Usage is implied rather than specified.

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.