Skip to main content
Glama
Sign In
Soul

Soul

by choihyunsus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

n2_mimir_study_sessions

Find unfinished durable study collections within a project scope to help agents resume prior study work.

Instructions

Find unfinished durable study collections in one scope.

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": {
      "project": "<project>"
    },
    "name": "n2_mimir_study_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNo
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv9.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It hints at filtering ('unfinished', 'durable') but never states that this is a read-only operation, whether it returns all matches or a page, ordering, or whether it requires an active session. 'Durable' is unexplained jargon.

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?

A single short sentence with the resource and the qualifier front-loaded; nothing is padded or redundant. Its brevity is efficient even if the content is thin.

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?

No annotations, no output schema, and zero parameter documentation mean the description is the only source of truth, and one sentence cannot cover it. An agent lacks the return shape, the scoping rules, and the relationship to study_start/study_add/study_end.

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% for two parameters, so the description must compensate and does not. 'In one scope' vaguely gestures at scoping but never says whether scope is set by 'project' (required) or 'agent' (optional), nor what an agent string means in this context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'find' and the qualifier 'unfinished durable study collections' give a rough idea of a list/search operation, but 'study collections' does not match the tool name's 'study_sessions' and nothing distinguishes it from siblings such as n2_mimir_recall, n2_mimir_lessons, or n2_work_sessions. An agent can guess it is a read/list operation but cannot confidently tell what a 'collection' is or how it relates to study_start/study_add/study_end.

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 when-to-use guidance, no exclusions, and no named alternative. With nine Mimir siblings plus generic work-session and recall tools, the agent is left to infer entirely on its own when this tool is the right choice.

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