Skip to main content
Glama

indonesia_license_enterprise

Read-only

One-time $700 USDC for the Enterprise licence: 90 days of unmetered access to 19 Indonesian data endpoints, delivered as a signed Bearer token inside this tool result. Depth: up to 3,650 /series prints in one request (more than 10 years of daily history, back to 2012), and the ?format=csv|jsonl bulk export of the whole series. 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_enterprise"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior2/5

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

The description is unusually candid about cost, delivery mechanism (token inside the result), and how to present it (Authorization: Bearer). However, it describes a $700 USDC charge and licence issuance while annotations declare readOnlyHint=true, which an agent could read as a free, side-effect-free call — a meaningful safety mismatch on a spend operation.

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?

Three densely packed sentences front-load price, tier, and deliverable, then move to capability and verification. Some phrasing ("more than 10 years of daily history, back to 2012", the no-account/no-key list) is promotional, but it carries usable facts rather than filler.

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 zero-parameter purchase tool with no output schema, it covers cost, duration, scope, what the result contains, how to use the token, and how to self-verify before paying. The only omission is the payment mechanics themselves, which the referenced /license endpoint presumably supplies.

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?

Zero parameters, so the schema baseline is 4. The description still adds meaning beyond the empty schema by documenting the ?format=csv|jsonl export option and the required Authorization header, which are call conventions the agent would not otherwise know.

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 specific verb and resource plus terms: a one-time $700 USDC purchase of a 90-day Enterprise licence covering 19 Indonesian endpoints, returned as a signed Bearer token. The tier is named explicitly, which cleanly separates it from the sibling licence tools (indonesia_license_growth, indonesia_license_newsroom, indonesia_license_pilot).

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 pre-purchase routing: "Check before paying" points the agent at GET /license for the full ladder and GET /series/preview to verify depth and hash. It does not explicitly state when to choose the cheaper sibling tiers instead, so the agent must infer that from the other tools' definitions.

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