Skip to main content
Glama

get_session_trigger_context

Read-onlyIdempotent

Returns the trigger and execution that originated a session from a session_id, enabling reverse lookup and traceability of session origins.

Instructions

Reverse lookup: given a session_id, returns the trigger and execution that originated the session

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": {
      "session_id": "<session_id>"
    },
    "name": "get_session_trigger_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesSession session_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / session_id / description
      Previous value: -"session_id da sessão"New value: +"Session session_id"
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety and mutability are settled. The description adds the useful behavioral fact that this traces provenance rather than returning session content, but with no output schema it should say more about the returned shape or what happens when a session has no originating trigger.

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 tight sentence, front-loaded with the 'Reverse lookup' label so the mental model arrives first. The 'given a `session_id`' clause mildly restates the required schema field, a small but real redundancy.

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 one-parameter read tool with rich annotations this is close, but the absence of an output schema means the description should characterize the return value's structure (and any empty-result behavior) more than it does. It states the return concept without enough shape for an agent to predict the payload.

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 coverage is 100%, though the schema's own text ('Session session_id') is tautological. The description clarifies the parameter's role as the lookup key whose originating trigger and execution are being resolved, which is a modest gain over the schema and lands at the baseline.

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 gives a specific verb-plus-resource framing: a reverse lookup from a session_id to the trigger and execution that created the session. That distinguishes it conceptually from siblings like get_session_history or get_trigger_execution, though it never names an alternative explicitly. The core operation is unmistakable.

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?

Usage is only implied by the phrase 'reverse lookup' and the origin-tracing framing; there is no explicit statement of when to pick this over get_session_history or get_trigger_execution. An agent can infer the scenario but must reason about the boundary itself.

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