Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_manager_session_current_state

Read-only

MANAGER READ: bounded canonical Session Manager current state.

Instructions

MANAGER READ: bounded canonical Session Manager current state.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum session documents to return, newest first; default 12, clamped to 1-20.
topicNoSession topic to read, cut at 128 characters; default management. Falls back to the manager's own thread, then to documents that mention the topic.management

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.67
    • addedInput schema / properties / limit / description
      Added value: +"Maximum session documents to return, newest first; default 12, clamped to 1-20."
    • addedInput schema / properties / topic / description
      Added value: +"Session topic to read, cut at 128 characters; default management. Falls back to the manager's own thread, then to documents that mention the topic."
  2. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the schema documents the limit clamp (1-20) and date scoping. The description adds only 'bounded canonical', which is vague and largely restates the limit behavior already in the schema. No mention of fallback ordering or what the returned state covers beyond the property descriptions.

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 front-loaded line with no padding. Brevity is fine, but the word choice ('bounded canonical') trades clarity for terseness.

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?

An output schema exists, so return values needn't be explained, and the parameters are well documented in the schema. But for a tool with many session-related siblings, the description leaves the agent without guidance on selection, scope, or what 'canonical current state' actually resolves to.

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

Parameters3/5

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

Schema description coverage is 100%, with clear per-parameter text for limit and topic, including the fallback chain. The description adds nothing beyond that, so the baseline of 3 applies.

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?

States a verb ('read') and a resource ('Session Manager current state'), which is enough to distinguish it from the write sibling aiworkhub_manager_session_write. However, 'bounded canonical' is opaque jargon and 'current state' does not say what the state actually contains.

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?

No indication of when to prefer this over aiworkhub_dashboard_sessions or how it relates to aiworkhub_manager_session_write. The agent must infer usage from the name alone.

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