Skip to main content
Glama

Kobo Terminal NGX

Single index

get_index
Read-onlyIdempotent

One NGX index by code or slug. Plan: Free+.

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": {
      "code": "<code>"
    },
    "name": "get_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesIndex code or slug, e.g. ASI, NGX30, ngx-bnk. Example: NGX30

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context in the plan gate, but says nothing about behavior on an unknown code/slug or what a lookup returns.

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?

Two short fragments, front-loaded with the core purpose, with no wasted clauses. The telegram-style 'Plan: Free+.' is terse to the point of being opaque about what the tier notation means.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter lookup with rich annotations, the description is close to adequate, but with no output schema it gives no hint whether the result is index metadata, current level, or constituent data. The 'Free+' tier notation is left unexplained.

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?

With one parameter at 100% schema coverage, the schema already documents 'code' with examples (ASI, NGX30, ngx-bnk). The phrase 'by code or slug' merely restates that field and adds no new meaning, so the baseline 3 applies.

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 gives a specific resource and lookup key: a single NGX index retrieved by code or slug. It implicitly contrasts with singular/plural siblings like list_indices and get_index_history, though it never names them explicitly, so an agent must infer the boundary rather than read it.

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?

'Plan: Free+' is the only conditional guidance offered, acting as an access-tier prerequisite. There is no explicit statement of when to pick this over list_indices (discovery) or get_index_history (time series), leaving that inference entirely to the agent.

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