Skip to main content
Glama
Sign In
SAGE

SAGE

by PsYcGoD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sage_agentic_session

Get the current agentic session state — failure streak, recent errors, intent chain. Useful for understanding context before deciding next action.

Instructions

Get the current agentic session state — failure streak, recent errors, intent chain. Useful for understanding context before deciding next action.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.6.2
  2. Removedv2.5.1
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Only states what is retrieved but not behavioral traits like idempotency, side effects, or permissions. For a read-only tool, more disclosure would help, e.g., that it does not modify state.

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?

Single sentence that is concise and front-loaded with action and key contents. No unnecessary words.

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?

No output schema, and description only lists components (failure streak, recent errors, intent chain) without specifying return format (e.g., JSON object). Adequate for a simple tool, but could be more complete with structure details.

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

Parameters4/5

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

No parameters, so schema coverage is 100%. Description adds no parameter info, but none is needed. Baseline score of 4 applies.

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?

Description clearly states verb 'Get' and resource 'current agentic session state' with specific items (failure streak, recent errors, intent chain). Differentiates from siblings like sage_agentic_fix and sage_agentic_run which are for fixing or running, not retrieving state.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Useful for understanding context before deciding next action', providing clear context. Does not list when not to use or alternatives, but the purpose naturally distinguishes it from sibling tools.

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