Skip to main content
Glama
Sign In
Integration Quest

Integration Quest

by MattCarpenter-Workato
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

rest

Recover uptime and API credits by resting, with a 20% chance of triggering a random encounter.

Instructions

Rest to recover Uptime and API Credits. Warning: 20% chance of triggering a random encounter!

Returns: Rest results and possible encounter

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Without annotations, the description partially discloses behavior: it recovers Uptime and API Credits and has a 20% random encounter chance. However, it does not state if resting consumes turns or has other side effects, leaving some behavioral gaps.

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?

The description is concise with two sentences. The first sentence states the primary purpose, and the second adds an important warning. No redundancy, well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, the description adequately explains return values ('Rest results and possible encounter'). It covers the tool's core function and risk, though could elaborate on what rest results entail.

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?

The tool has no parameters, so the description does not need to provide param info. The input schema is fully covered. Baseline for 0 parameters is 4.

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 clearly states the tool's purpose: resting to recover Uptime and API Credits. It also mentions a random encounter risk, adding specificity. While it distinguishes from siblings like 'attack' or 'explore', it does not differentiate from other recovery methods like 'use_item'.

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?

The description implies when to use (when needing to recover resources) but does not provide explicit guidance on when not to use or mention alternatives. The warning about random encounters adds context.

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