Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_manager_context_graph_range

Read-only

Retrieve a bounded transcript range around a specific event in a conversation thread, including configurable before and after events for precise context review.

Instructions

MANAGER READ: retrieve an exact bounded transcript range around one event.

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": {
      "thread_id": "<thread_id>",
      "around_event_id": "<around_event_id>"
    },
    "name": "aiworkhub_manager_context_graph_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoEvents to include after the center; default 5, clamped to 0-50.
beforeNoEvents to include before the center; default 5, clamped to 0-50.
thread_idYesConversation thread the event belongs to: letters, digits and _ . : -, starting with a letter or digit, at most 256 characters.
around_event_idYesPositive integer id of the center event within thread_id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.12.67
    • addedInput schema / properties / after / description
      Added value: +"Events to include after the center; default 5, clamped to 0-50."
    • addedInput schema / properties / around_event_id / description
      Added value: +"Positive integer id of the center event within thread_id."
    • addedInput schema / properties / before / description
      Added value: +"Events to include before the center; default 5, clamped to 0-50."
    • addedInput schema / properties / thread_id / description
      Added value: +"Conversation thread the event belongs to: letters, digits and _ . : -, starting with a letter or digit, at most 256 characters."
  2. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds little beyond repeating that this is a read operation and saying the range is bounded, which is also implied by the schema's before/after clamping.

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?

It is a single front-loaded fragment with zero filler. The core operation and scope are immediately visible.

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?

For a simple four-parameter read tool with a full schema, annotations, and an output schema, the description covers the basic purpose. However, it omits sibling routing and any behavior around missing events or ordering, leaving meaningful context gaps.

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%, so the parameters are already fully documented in the schema. The description only implicitly maps to around_event_id and the bounded range, adding no syntax or edge-case meaning beyond the structured fields.

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

Purpose4/5

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

The description states a specific verb and resource: retrieve a bounded transcript range around one event. It is clear enough to distinguish a range-around-event read from a general graph search, though it never names the sibling tools it differs from.

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?

It implies usage by saying 'around one event', but gives no explicit when-to-use guidance or alternatives such as context_graph_search or context_graph_related. An agent must infer the routing decision from the tool name and schema.

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