SymKit

Overview Schema Source Related Servers Discussions Admin

list_assumptions

Retrieve assumptions at global, domain, session, or step level, or merged across all levels for symbolic computation review.

Instructions

    📐 List assumptions at a specific level or merged across all levels.

    Args:
        level: "global", "domain", "session", "step", or None for merged

    Returns:
        Assumptions at the requested level

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

Input Schema

Name	Required	Description	Default
`level`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 8, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes a read-only operation but does not explicitly state side effects (or lack thereof). It does not mention authorization needs, rate limits, or other behavioral traits beyond listing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is exceptionally concise with two sentences and a returns line. It is front-loaded with the purpose and efficiently explains the parameter and output without unnecessary detail.

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

Completeness5/5

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

Given the tool's low complexity (one optional parameter, has output schema), the description is complete. It explains what the tool does, how to use the parameter, and what is returned.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description's Args section clearly explains the 'level' parameter with enumerated options ('global', 'domain', 'session', 'step', or None for merged). This adds significant meaning beyond the schema's generic anyOf definition.

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 action 'List assumptions' and specifies the resource ('assumptions at a specific level or merged across all levels'). It distinguishes from sibling tools like 'assume' and 'show_assumptions' by focusing on listing with level granularity.

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 implies usage when needing to list assumptions at different levels, but does not explicitly state when to use this tool over alternatives like 'show_assumptions' or 'check_assumption_conflicts'. No exclusions or when-not-to-use guidance provided.

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