Skip to main content
Glama

Tipline: unofficial GTA 6 guide

Get one guide entry

get_gta6_entry
Read-onlyIdempotent

Get the full text (markdown) of one Tipline entry by id, with its sources.

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": {
      "id": "<id>"
    },
    "name": "get_gta6_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEntry id from search or list results, e.g. 'lucia-caminos'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"Entry id from search or list results, e.g. 'lucia-caminos'"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description's useful addition is the return shape – markdown full text plus sources – which matters because there is no output schema. It says nothing about behavior on an unknown id (error vs empty).

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 front-loaded sentence that identifies verb, resource, return format and key with zero padding. Nothing could be removed without losing information.

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 one-parameter read tool with no output schema, stating that the result is full markdown text with sources covers what an agent needs to know about the return. Only the missing-id behavior and the naming slip between 'Tipline' and the GTA6 guide leave small gaps.

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?

One parameter at 100% schema coverage, including a concrete example value, so the schema already does the heavy lifting. The description only restates that the call is by id, adding no format or sourcing detail beyond the schema. Baseline 3 applies.

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?

A specific verb and resource: gets the full markdown text of one entry plus its sources, keyed by id. It implicitly distinguishes itself from the list/search siblings by returning one entry's full text, though it never names them. Minor friction: it calls the resource a 'Tipline entry' while the tool name and siblings say GTA6 guide.

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?

Usage is only implied – 'by id' plus the schema note 'Entry id from search or list results' suggests the flow of searching first and then fetching, but the description itself states no when-to-use condition and no explicit alternative. An agent can infer the routing, but must do the work.

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