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

io.github.tammy357/ts-second-opinion

by tammy357

benchmark_summary

Summarize benchmark results for transition-state validation, including geometry and handedness error rates before and after repair, mirror-image catches, trust metrics, and risk-coverage curves.

Instructions

Headline results, split into geometry errors and handedness errors: rates before and after, how many wrong-handed guesses the rules catch and how many are whole mirror images (same energy, so even DFT would not flag them), certified-trust numbers, and risk-coverage curves.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral load. It discloses the categories of results and a useful domain detail about mirror-image errors not being caught by DFT, but it does not state that the tool is read-only, whether it depends on prior evaluations, or how expensive or limited the call is.

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?

It is a single front-loaded sentence that avoids unnecessary preamble. The colon-delimited list is dense but every clause contributes to defining the summary's contents, though the parenthetical could be tightened.

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?

With no output schema, the description must explain the returned content, and it does list the major result categories. However, it leaves the structure and interpretation of 'rates before and after' ambiguous and gives no prerequisites or relationship to the evaluation and certification tools, so it is only adequate for a zero-parameter summary endpoint.

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?

There are zero input parameters, so there is no parameter semantics to explain; the baseline for an empty schema is 4. The description does not need to add argument meaning.

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?

The description states that it returns headline results and enumerates the specific breakdowns: geometry vs. handedness errors, before/after rates, mirror-image counts, certified-trust numbers, and risk-coverage curves. This makes the resource clear, but it never uses an explicit verb such as 'returns' and does not distinguish it from siblings like evaluate_predictions or certify_trust.

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 explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The phrase 'Headline results' only implies it is a summary view; an agent must still infer whether to call this instead of evaluate_predictions, gate_check, or certify_trust.

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