Skip to main content
Glama

Sixfigs

List money methods

get_money_methods
Read-onlyIdempotent

Returns the ways to earn in-game money in Grand Theft Auto VI that are in the Sixfigs dataset, each with payout per run, time per run, dollars per hour where a run time is reported, unlock chapter and requirement, status and sources. Use this when the user asks how to make money in the game or how money methods compare. Ordered by reported dollars per hour; methods without a reported run time are listed separately without a rate. Pass max_chapter to leave out methods from later chapters. Facts are compiled from named sources after the game's 19 Nov 2026 release; each result shows its status (official, confirmed, single-source or disputed), sources and verified date.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum methods per list (default 10).
max_chapterNoStory chapter the player has reached. Content from later chapters is left out. Without it, major story spoilers are left out.

Output Schema

NameRequiredDescriptionDefault
urlYes
methodsYes
unratedYes
disputedYes
maxChapterYes
verifiedOnYes
lockedCountYes
spoilerNoteYes

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?

Annotations already declare this is a safe, idempotent, closed-world read; the description goes well beyond them by disclosing the sort order (reported dollars per hour), the handling of methods lacking a run time (listed separately, no rate), the default spoiler-suppression behavior, and the provenance/status model (official, confirmed, single-source, disputed) with verified dates. That is exactly the extra context an agent needs to interpret results without ambiguity.

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?

Purpose and use case are front-loaded, and the remaining sentences each carry real information (ordering, no-rate bucket, chapter filtering, provenance). It is dense but a few clauses, such as the repeated explanation of status values, could be tightened without losing meaning.

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?

An output schema exists, so return values need not be detailed, yet the description still characterizes the field set and the ordering logic. Given the tool's complexity (provenance states, spoiler rules, post-release data), the description covers everything an agent needs to call it correctly and read results sensibly.

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 description coverage is 100%, so both parameters are already documented and the description only restates the max_chapter behavior already spelled out in the schema. The limit parameter is never mentioned in the description, and no new syntax or edge-case meaning is added, so this sits at the high-coverage baseline.

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 opens with a specific verb and resource ('Returns the ways to earn in-game money ... in the Sixfigs dataset') and enumerates the returned fields, so the agent knows exactly what the tool produces. It stops short of naming a sibling such as plan_money to contrast against, so differentiation is only implied by the 'how to make money / how methods compare' use case.

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 an explicit trigger ('Use this when the user asks how to make money in the game or how money methods compare') plus a conditional usage note for max_chapter to suppress later-chapter content. What is missing is any when-not-to-use statement or pointer to an alternative like plan_money, so the agent must infer the boundary itself.

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