Skip to main content
Glama
io.github.tammy357/ts-second-opinion

io.github.tammy357/ts-second-opinion

by tammy357

audit_rdb7_dataset

Audits RDB7 reactions for mismatches between reactant or product geometry and atom-mapped SMILES, flagging atoms at bonding distance without bonds or bonds whose atoms are far apart.

Instructions

Data-quality audit of RDB7: reactions whose reactant or product geometry contradicts the atom-mapped SMILES (atoms at single-bond distance that the SMILES does not bond, or a SMILES bond whose atoms are far apart). Uploaded reactions get the same check automatically (input_warnings in triage_structures).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "audit_rdb7_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the audit criterion well, but does not state whether the tool is read-only, what it returns, whether it reports counts or examples, or how expensive it is to run.

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?

The description is front-loaded and every sentence contributes: the first defines the audit and its rule, the second clarifies how uploaded reactions are handled elsewhere. The parenthetical detail is useful, though the long first sentence is dense.

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?

For a zero-parameter tool, the description explains the check but leaves the result shape unspecified. Since there is no output schema or annotation coverage, an agent still lacks a clear expectation of what the audit returns.

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?

The tool has zero parameters, so there are no parameter semantics for the description to add. The baseline for a parameterless tool is 4.

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?

The description gives a specific verb and resource: "Data-quality audit of RDB7" and then defines the exact check (reactant/product geometry contradicting atom-mapped SMILES). It also distinguishes the dataset-level audit from the automatic check on uploaded reactions handled via triage_structures.

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?

Usage is implied: this audits the RDB7 dataset, while uploaded reactions are covered automatically in triage_structures. However, there is no explicit when-to-use or when-not-to-use guidance, and no alternative is named as the preferred path for other cases.

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