SymKit

Overview Schema Source Related Servers Discussions Admin

session_start

Initiate a symbolic derivation session by providing a name, domain, and pattern to begin step-by-step mathematical transformations with full provenance.

Instructions

    Start a new derivation session

    Args:
        name: Derivation name
        description: Derivation description
        domain: Math/physics domain tag
        pattern: Derivation pattern
        goal: Natural-language goal (optional)
        author: Author

    Returns:
        Session information

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>"
    },
    "name": "session_start"
  }
}

Input Schema

Name	Required	Default
`goal`	No
`name`	Yes
`author`	No
`domain`	No	general
`pattern`	No	direct-manipulation
`description`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 8, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description itself must disclose side effects and required context. It only states it starts a session and returns session info, but omits details like authentication needs, concurrency issues, or what happens if a session with the same name exists.

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 and uses a clear Args/Returns structure. However, the Returns section could be more detailed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 6 parameters with zero schema descriptions and a complex tool ecosystem, the description fails to provide sufficient context. It does not explain how it relates to sibling session tools or what output schema details are important.

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%, and the description merely lists parameter names without explaining their meaning, valid values, or how they affect behavior. For example, 'domain' defaults to 'general' but no clarification of allowed domains is provided.

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 'Start a new derivation session', specifying the verb and the resource. This distinguishes it from sibling session tools like session_list or session_resume.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it explain prerequisites or when not to use it.

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