Skip to main content
Glama
Sign In
SymKit

SymKit

by LBurny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

session_verify_step

Re-verify a step in the current symbolic computation session to validate derivation correctness. Specify step number, or leave empty for the last step.

Instructions

Re-verify a single step in the current session.

    Args:
        step_number: 1-based step number. Defaults to -1 (last step).

    Returns:
        Verification result.

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

Input Schema

NameRequiredDescriptionDefault
step_numberNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states 're-verify' and returns a 'verification result', but does not indicate side effects (e.g., whether it modifies state) or details about the result.

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 concise with a clear first sentence stating the main action, followed by parameter details. No superfluous text.

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?

Given the existence of an output schema, the description provides adequate context for a simple verification action. However, it could mention prerequisites (active session) and that it is typically used after step modifications.

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?

Schema coverage is 0%, so the description compensates well by explaining the parameter's purpose, that it is 1-based, and the default behavior. This adds significant meaning beyond the bare schema.

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 clearly states the verb 're-verify' and the resource 'a single step in the current session'. This distinguishes it from siblings like 'session_verify_session' which verifies the entire session.

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?

The description explains the purpose but does not provide explicit guidance on when to use this tool versus alternatives. There are no 'when not to use' statements or references to other tools.

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

Deploy Server

Other Tools