Extend Session
extend_sessionExtend your session by setting a duration from 0 to 9 minutes to control vaporizer usage.
Instructions
Set session extension value from 0 to 9.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| minutes | Yes |
extend_sessionExtend your session by setting a duration from 0 to 9 minutes to control vaporizer usage.
Set session extension value from 0 to 9.
| Name | Required | Description | Default |
|---|---|---|---|
| minutes | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description does not disclose behavioral traits such as whether setting a value overrides or extends an existing session, or if it requires an active session. The tool's behavior remains opaque.
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?
The description is a single sentence, which is concise, but it lacks structure and does not earn its place by providing valuable context beyond the title. It could be expanded meaningfully.
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?
No output schema, no annotations, and the description does not explain return values, errors, or side effects. Given the existence of sibling tools like start_session, the description leaves important gaps.
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 0%, and the description adds no meaning beyond the schema's existing constraints (integer 0-9). It does not explain what 'minutes' represents or how it affects the session.
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?
The description clearly states the verb 'Set' and the resource 'session extension value' with a numeric range 0-9. However, it does not differentiate from sibling tools like start_session, leaving the exact meaning of 'extend' ambiguous.
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?
No guidance on when to use this tool versus alternatives like start_session. The description does not indicate prerequisites, side effects, or appropriate contexts for setting the extension.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nidamen/drdabber-switch2-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server