Skip to main content
Glama

Tipline: unofficial GTA 6 guide

List guide entries

list_gta6_entries
Read-onlyIdempotent

List Tipline entries (id, title, summary, url), optionally filtered by type.

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

Input Schema

NameRequiredDescriptionDefault
typeNoOptional entry type filter, e.g. 'vehicle'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / type / description
      Added value: +"Optional entry type filter, e.g. 'vehicle'"
  2. First observed

TDQS

B3.4/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 safety is covered; the description usefully adds the shape of each returned item. It says nothing about volume, ordering, or whether all entries are returned at once versus paginated, which matters for a list tool.

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?

A single front-loaded sentence with no filler; the parenthetical field list earns its place by compensating for the absent output schema. Minor deduction for the unexplained 'Tipline' label that doesn't match the tool name or title.

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

Completeness3/5

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

For a one-optional-parameter list tool with rich annotations, the definition covers purpose, return fields, and the filter. What remains unaddressed is enumeration behavior — result caps, ordering, or emptiness handling — which an agent would want before calling this to scan a full corpus.

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% and the single parameter carries both an enum of valid types and an example ('vehicle'), so the description adds little beyond noting the filter is optional. Baseline 3 applies when the schema does the heavy lifting.

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 ("List Tipline entries") and even enumerates the returned fields (id, title, summary, url). It does not explicitly distinguish itself from search_gta6_guide or get_gta6_entry, and the "Tipline" wording diverges from the tool name/title ("guide entries"), but the core purpose is unambiguous.

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?

The phrase "optionally filtered by type" implies the primary use case and that the filter is not required, but there is no explicit when-to-use vs. when-to-use-search guidance despite siblings like search_gta6_guide and get_gta6_entry. An agent must infer that this is the enumerate-everything path and search is the query path.

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