Skip to main content
Glama

try_free

Free, no key needed: run one of Kula Labs' own products for real, 3 times a day (with a key, your own 3; without, a shared pool). Swiss QR code, IBAN check, UID check, JSON repair, cron, calendar invite and more: pick a listing by Kula Labs from ask_market or search_listings, pass its listing_id and an input matching its input_schema (get_listing). Nothing is charged or stored; the answer shows the result and how to buy more.

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": {
      "listing_id": "<listing_id>"
    },
    "name": "try_free"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputNothe input the product needs, matching input_schema from get_listing
listing_idYesa listing sold by Kula Labs (ask_market, search_listings)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that nothing is charged or stored, that usage is capped at 3/day (own quota with a key, shared pool without), and that the response contains the result plus an upsell path. This is exactly the cost, persistence, and rate-limit context the readOnlyHint=false / destructiveHint=false annotations cannot convey.

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?

Front-loads the key selling point (free, no key needed) and the quota before the mechanics. The middle clause listing example products is dense but earns its place by helping an agent recognize applicable tasks; the only waste is a mild run-on structure that packs discovery, schema, and pricing into one breath.

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?

Covers what an agent needs for a nested-input call: which listings qualify, how to obtain the nested input schema, and what the response contains, with no output schema required. It stops short of describing failure modes, such as what happens when the daily quota is exhausted or the shared pool is empty.

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 field descriptions already say listing_id is a Kula Labs listing and input must match input_schema from get_listing. The description restates those constraints rather than adding new syntax, format, or validation meaning, so the baseline 3 applies; its only marginal addition is naming the discovery tools for finding a valid listing_id.

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?

States a concrete verb and resource: run one of Kula Labs' own products for free, three times a day. It explicitly narrows scope to Kula Labs listings, which separates it from the sibling try_my_listing (testing your own listing) and from buy (paid access), and it enumerates example products (Swiss QR code, IBAN check, cron) so an agent knows the class of work it covers.

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?

Gives clear preconditions and a workflow: find a Kula Labs listing via ask_market or search_listings, fetch its input_schema via get_listing, then call this tool with listing_id and matching input. It also explains the quota difference between keyed and keyless use, implying when to move to paid access. It does not explicitly state a when-not condition or name the buy tool as the escalation 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