Skip to main content
Glama

Sixfigs

Plan money for a target

plan_money
Read-onlyIdempotent

Builds a money plan for Grand Theft Auto VI from the Sixfigs dataset: given the player's story chapter, a target amount and the minutes available, returns which methods to run, how many times, expected earnings, dollars per hour, unlock requirements and verified dates. Use this when the user wants to reach a specific amount of in-game money in a set time. Only methods unlocked by the given chapter, with a reported run time and not disputed, are planned; earnings use the lowest reported payout. The chapter also filters spoilers.

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": {
      "chapter": "<chapter>",
      "target": "<target>",
      "minutes": "<minutes>"
    },
    "name": "plan_money"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesTarget amount of in-game dollars.
chapterYesStory chapter the player has reached. Also used as max_chapter for spoiler filtering.
minutesYesReal-time minutes the player has available.

Output Schema

NameRequiredDescriptionDefault
urlYes
inputYes
stepsYes
totalMaxYes
totalMinYes
shortfallYes
verifiedOnYes
lockedCountYes
minutesUsedYes
unratedCountYes
disputedCountYes
reachesTargetYes
availableMethodsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses the planning rules that shape results: only methods unlocked by the chapter, with a reported run time and not disputed, and earnings computed from the lowest reported payout. It also flags that the chapter argument affects spoiler filtering, which the agent could not infer from the safety hints alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences: purpose and inputs, then when to use, then planning constraints. Dense but every clause carries information; the long output enumeration is slightly redundant given an output schema exists.

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

Completeness5/5

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

For a three-required-parameter read-only planning tool with a full schema and an output schema, the description covers inputs, selection criteria, when to call it, and the meaning of the returned plan. Nothing an agent needs to invoke it correctly is missing.

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

Parameters3/5

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

Schema coverage is 100%, so every parameter is already documented, and the description largely restates chapter, target and minutes. It adds a little meaning by explaining that chapter constrains unlocked methods and spoiler filtering, but nothing beyond what the schema field description for chapter already states.

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 names a specific verb and resource ('Builds a money plan for Grand Theft Auto VI from the Sixfigs dataset') and enumerates the outputs, so an agent can tell what the tool produces. It never names or contrasts a sibling such as get_money_methods, so the differentiation is implied rather than explicit.

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

Usage Guidelines4/5

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

It gives a clear triggering condition: 'Use this when the user wants to reach a specific amount of in-game money in a set time.' It does not state when not to use it or point to an alternative for exploration-style queries, which is the only gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources