Skip to main content
Glama
Sign In
Integration Quest

Integration Quest

by MattCarpenter-Workato
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

move

Navigate to an adjacent system using cardinal directions to explore new rooms and advance in an integration-themed text-based RPG.

Instructions

Navigate to an adjacent system.

Args: direction: Cardinal direction to move

Returns: New room description or failure message

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": {
      "direction": "<direction>"
    },
    "name": "move"
  }
}

Input Schema

NameRequiredDescriptionDefault
directionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility. It mentions return values ('New room description or failure message') but omits details such as obstacles, resource consumption, or side effects.

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 brief and well-structured, with a one-line summary followed by clear Args/Returns sections. Every sentence serves a purpose.

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 tool's simplicity (1 parameter, output schema present), the description covers the main functionality. However, it could mention edge cases or prerequisites for a higher score.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only paraphrases the parameter type ('Cardinal direction to move'), adding no new information beyond the enum values in the schema.

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?

The description clearly states 'Navigate to an adjacent system' with a specific verb and resource, and the direction parameter is well-defined. Among sibling tools like 'explore' and 'flee', this tool is uniquely positioned for cardinal movement.

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

Usage Guidelines2/5

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

No explicit guidance is provided on when to use this tool versus alternatives like 'explore' or 'flee'. The description implies basic movement but does not specify exclusions or 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