sessions_get_settingsRetrieve a StreamElements channel's session settings to see when the session resets and which events count toward it. Use this to configure or verify session tracking.
Get the channel's session settings, such as when the session resets and which events count toward it.
| Name | Required | Description | Default |
|---|---|---|---|
| channel | No | StreamElements channel id (24-char hex). Defaults to SE_CHANNEL_ID or the channel that owns the token. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful content context by enumerating what the settings include (reset timing, event counting), but says nothing about authorization requirements beyond the schema's defaulting note, nor about rate limits or freshness.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, front-loaded with the verb and resource, with the trailing clause earning its place by defining what "settings" means. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple zero-required-parameter read with annotations covering safety and a fully documented schema, the description is nearly sufficient; the parenthetical content hint partly compensates for the absent output schema. The remaining gap is that the return shape is only gestured at rather than characterized.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%: the single `channel` parameter already documents the 24-char hex format and the SE_CHANNEL_ID fallback. The description adds no parameter-level detail, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ("Get the channel's session settings") and even names the kind of content returned (reset timing, qualifying events). It is clear what the tool does, but it never distinguishes itself from the close siblings sessions_get or sessions_update_settings, so an agent must infer the boundary from the name alone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use statement, no condition selecting it over sessions_get, and no mention that its counterpart sessions_update_settings exists. The only guidance is implied by the verb "Get"; nothing tells the agent when this read is the right call.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.