Skip to main content
Glama
Amazing Cultivation MCP

Amazing Cultivation MCP

acsmcp_guide

Returns the recommended observe-decide-act-verify loop and argument recipes for playing Amazing Cultivation Simulator reliably, helping agents structure game actions and verify results.

Instructions

Return the recommended observe-decide-act-verify loop and argument recipes for reliably playing ACS.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it does disclose the substance of what is returned (a loop plus argument recipes) with no indication of side effects, consistent with a zero-argument read. It stops short of describing output format, length, or whether the content is static versus account-specific.

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?

A single sentence with zero filler, front-loaded on the return value, with the qualifier 'for reliably playing ACS' placed where it adds context rather than padding.

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?

For a zero-param, no-output-schema guidance tool, the description covers what comes back well enough to call it correctly. A sentence on when to reach for it relative to acsmcp_methods and acsmcp_call would close the remaining gap.

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 takes zero parameters and the schema is fully closed (additionalProperties: false), so there is nothing parameter-level to explain; baseline for 0 params applies. The reference to 'argument recipes' is a nice hint that it documents args for sibling calls rather than accepting any itself.

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?

States a specific verb and resource: it returns the recommended observe-decide-act-verify loop plus argument recipes. That is clearly distinct from a method-listing or invocation tool, though the description never names or contrasts the siblings (acsmcp_call, acsmcp_methods), and the acronym 'ACS' is never expanded.

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?

'for reliably playing ACS' implies this is a read-first orientation step, but the description never says when to call it versus acsmcp_methods, nor whether it should be called before acsmcp_call. Usage is inferable but not stated or bounded.

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