Skip to main content
Glama
Sign In

SparkAds

by dev.sparkads
OverviewDiscussionsAdmin

list_free_slots

Read-onlyIdempotent

List the UTC hours nobody has claimed yet, out of the 24 the network sells. Pass a country to also get each free hour on that country's clock and the best five ranked by local evening attention. Supported countries: GB, IE, PT, FR, DE, ES, IT, NL, BE, SE, NO, DK, PL, CH, AT, NG, FI, GR, RO, UA, EG, ZA, IL, SA, TR, RU, KE, AE, PK, IN, BD, TH, VN, ID, CN, SG, MY, PH, HK, TW, AU, JP, KR, NZ, BR, AR, US, CA, PE, CO, MX. Read-only; claiming an hour still happens on the website.

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

Input Schema

NameRequiredDescriptionDefault
countryNoISO-3166 alpha-2 country code, e.g. GB or US. Adds local times and peak suggestions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already cover read-only and idempotent behavior, but the description adds important workflow context: claiming is not performed here and must happen on the website. It also describes the enriched output when country is supplied, though it does not discuss pagination or return formatting.

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 front-loaded with purpose and optional-parameter effect. The long inline list of supported countries is necessary because the schema lacks an enum, though it makes the description longer than ideal structurally.

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?

For a simple one-parameter read-only listing tool with rich annotations, the description covers purpose, optional parameter effects, supported countries, and the crucial boundary that claiming happens elsewhere. An agent has enough information to call it correctly.

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

Parameters4/5

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

The schema already documents the country parameter at 100% coverage, so the baseline is 3. The description adds meaningful detail by listing all supported country codes, which are not present as an enum in the schema, and clarifies the effect on local-clock values and best-five ranking.

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 states a specific verb and resource: list UTC hours nobody has claimed, out of the 24 the network sells. This clearly distinguishes it from siblings like get_slot or get_my_stats without requiring schema inspection.

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 clearly explains that passing a country adds local times and top-five recommendations, and that claiming happens on the website rather than through this tool. It lacks explicit when-not-to-use guidance or direct comparison with sibling tools such as get_slot, so it falls short of a 5.

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

All SparkAds toolsInspect
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