Skip to main content
Glama

indonesia_license_pilot

Read-only

One-time $99 USDC for the Pilot licence: 30 days of unmetered access to 19 Indonesian data endpoints, delivered as a signed Bearer token inside this tool result. Depth: up to 365 /series prints in one request. No account, no API key, no renewal charge: send the token as Authorization: Bearer . Check before paying: GET /license is the whole ladder as JSON and GET /series/preview proves the depth and its sha256.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial context beyond readOnlyHint: the exact price and asset ($99 USDC, one-time), that the deliverable is a signed Bearer token returned inside the tool result, that no account or API key exists, that there is no renewal charge, and the precise Authorization header format for reuse. The only unresolved tension is that readOnlyHint=true accompanies a paid issuance, and the description never states whether the USDC transfer happens inside this call or out-of-band after the token is returned.

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 price and the deliverable, then layers depth limits, auth usage, and pre-purchase checks in a compact sequence with no filler. It is dense to the point of being crammed into few sentences, and the pre-purchase check endpoints sit after the auth instructions rather than before the action recommendation.

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?

With no output schema, the description carries return-value disclosure and does it reasonably well by naming the Bearer token as the payload, plus price, duration, depth limit, and reuse instructions. It omits where in the result the token appears (field name/shape) and how expiry or invalid-token errors surface, which is the main remaining gap for a purchase tool.

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 tool takes zero parameters, so the schema-offered baseline of 4 applies; there is nothing for the description to disambiguate. Its references to GET /license and GET /series/preview are external verification endpoints rather than inputs to this tool, so they read as guidance rather than parameter documentation.

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 (buy/obtain), a concrete resource (the Pilot licence), and quantifies scope exactly: $99 USDC once, 30 days unmetered, 19 Indonesian endpoints, up to 365 /series prints per request. It also points at the tier ladder (GET /license) so an agent can place it among indonesia_license_growth / enterprise / newsroom without guessing.

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 selection context (when you need unmetered access across the Indonesian endpoint family) and an explicit prerequisite step: check GET /license and GET /series/preview before paying. It stops short of naming which sibling licence tier to choose instead when 30 days/19 endpoints is not the right fit, or when the metered preview/series tools suffice.

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