Skip to main content
Glama

gta-map-categories

List or search every GTA Online map category on GTALens, filtered by group, keyword, or money-only.

Instructions

List or search every GTA Online map category available on GTALens (street dealers, gun van, exotic exports, drug vehicle, collectibles, business missions, Cayo, properties, and ~100 more). Filter by group, keyword, or money-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupNo
searchNoKeyword to filter category names/slugs
moneyOnlyNoOnly money-relevant categories
Behavior3/5

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

No annotations are provided, so the description carries the burden. It describes the operation (list/search) without detailing behavioral traits like read-only, rate limits, or side effects. Since the operation is a simple query, it's adequate but not explicit.

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, well-structured sentence that front-loads the core purpose, provides concrete examples, and lists filtering options. No redundant information; every part earns its place.

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?

Given three optional parameters and no output schema, the description covers the tool's functionality adequately. It explains what it lists, gives examples, and mentions all filter options. It could be improved by noting return format or pagination, but is mostly complete for a simple listing tool.

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 67% with descriptions for search and moneyOnly. The description adds that these are filters, but doesn't explain group values or add significant detail beyond the schema. It meets the baseline for high-coverage schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists or searches GTA Online map categories, with specific examples (street dealers, gun van, etc.) and mentions over 100 categories. It differentiates from sibling tools that focus on specific categories or locations.

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?

The description explains filtering by group, keyword, or money-only, giving clear context on how to use the parameters. While it doesn't explicitly state when not to use it vs. sibling tools, the broad scope implies it's the general category lookup tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Zfinix/gta_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server