Sunset Strip: GTA 6

Top GTA 6 clippers

get_top_clippers

Read-only

Players whose GTA 6 clips get the most votes on Sunset Strip (this week or all time), with Daily Job wins, profile links and whether they are available for hire as clippers.

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_top_clippers"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`period`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context about returned fields such as Daily Job wins, profile links, and hire availability, but it does not explain ranking behavior, limit defaults, or response shape.

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?

The description is a single front-loaded sentence and avoids unnecessary repetition. It is dense but appropriately sized for a simple retrieval tool.

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 simple two-parameter read-only tool, the description covers the main resource and some return fields. However, it leaves the limit parameter undocumented, does not specify a default period, and does not clarify when to choose this over get_top_clips.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It explains the period values as 'week' or 'all time', but says nothing about the limit parameter, including its purpose, default, or maximum of 25.

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 clearly states the resource and ranking basis: players whose GTA 6 clips get the most votes on Sunset Strip. It implies a distinction from the sibling get_top_clips by focusing on players rather than clips, but it does not explicitly differentiate or route to that sibling.

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

Usage Guidelines2/5

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

It mentions the available periods ('this week or all time') but gives no guidance on when to use this tool versus get_top_clips or other sibling tools. There are no exclusions or alternatives named.

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

All Sunset Strip: GTA 6 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?