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

io.github.tammy357/ts-second-opinion

by tammy357

save_rule

Persist a validated rule check after re-testing on save; it is stored in tsso/checks_user by default and excluded from triage unless a person explicitly requests inclusion.

Instructions

Save a rule check that passes the gate (re-tested on save). By default it goes to tsso/checks_user and is not used in triage; set use_in_triage=True only when a person has asked for it.

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": {
      "name": "<name>",
      "rule_text": "<rule_text>",
      "python_source": "<python_source>"
    },
    "name": "save_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
rule_textYes
python_sourceYes
use_in_triageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the important traits: the rule is re-validated on save, it lands in a specific default location (tsso/checks_user), and it is excluded from triage unless explicitly opted in. It doesn't say what happens when the gate re-test fails, whether an existing rule with the same name is overwritten, or what the call returns.

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?

Two short sentences, front-loaded with the core action and precondition, then the storage/triage caveat. Nothing is padded, though the mid-sentence line break and the phrase "rule check that passes the gate" 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?

For a 4-parameter mutation tool with no annotations and no output schema, the description covers the write's destination and the triage opt-in, which are the highest-risk facts. It leaves out failure behavior on a failed gate re-test, overwrite/conflict semantics on name, and return expectations, so it is adequate but not complete.

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

Parameters2/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 only explains use_in_triage (default and the human-approval condition). The three required parameters — name, rule_text, and python_source — get no explanation of format, expected language, or relationship between rule_text and python_source.

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 names a specific verb and resource ("save a rule check") plus a precondition ("passes the gate, re-tested on save"), which is well beyond a restatement of the name. It doesn't explicitly contrast itself with siblings like list_rules or get_rule_source, but the operation is unambiguous.

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?

It gives a concrete usage rule for the one optional parameter: default is non-triage storage in tsso/checks_user, and use_in_triage=True only when a person has explicitly asked. No alternative tools are named for cases where the rule fails the gate, which keeps it from a 5.

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