API Indonesia

Get school by NPSN

sekolah_get

Read-onlyIdempotent

Get a single school by its NPSN (National School Identification Number).

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": {
      "npsn": "<npsn>"
    },
    "name": "sekolah_get"
  }
}

Input Schema

Name	Required	Description	Default
`npsn`	Yes	8-digit NPSN (e.g. "10100101")

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds no further behavioral context such as not-found handling, authentication requirements, or response shape. Given the strong annotation coverage, this is adequate but not enriched.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no redundant clauses. Every phrase contributes to identifying the operation and lookup key.

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?

This is a simple one-parameter read-only lookup with complete schema coverage and annotations covering the safety profile. The description is sufficient for correct invocation, though it does not mention not-found behavior or what school fields are returned.

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?

Schema description coverage is 100%, and the schema already documents the required 8-digit format with an example. The description adds useful meaning by expanding NPSN as "National School Identification Number", improving semantic understanding beyond the schema.

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 states the specific verb "Get", the resource "school", and the lookup key "NPSN". It makes the exact-identifier lookup intent clear versus sibling list/search tools, though it does not explicitly name sekolah_list or sekolah_search.

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

Usage Guidelines3/5

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

The phrase "by its NPSN" implies this tool should be used when an exact NPSN is known, and an agent can infer that browsing or broad search belongs to sibling tools. However, there is no explicit when-to-use, when-not-to-use, or named-alternative guidance.

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

All API Indonesia 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?