Skip to main content
Glama

National Capability Benchmark

List the nine dimensions

list_dimensions
Read-onlyIdempotent

The nine capability dimensions, the question each one answers, and how many indicators each has: scored, declared gaps, rejected, and conditions published beside it. Also the dataset version and the quoting contract. Start here.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds useful return-content information, including the per-dimension question, indicator counts, status categories, dataset version, and quoting contract, but it does not discuss pagination, formatting, or limits; given the annotations and simple zero-parameter nature, a 3 is appropriate.

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?

The description is compact and front-loads the main payload: the nine dimensions and their associated metadata. The phrasing is slightly telegraphic, especially "scored, declared gaps, rejected, and conditions published beside it," but every sentence contributes relevant information.

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?

For a zero-parameter, read-only metadata tool with no output schema, the description does a good job enumerating the returned contents and identifying itself as the starting point. It is not fully complete because terms like "quoting contract" and the exact meaning of the status categories are left unexplained.

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?

This tool has zero parameters, so the baseline is 4 per the rubric. The description appropriately spends no time on parameter semantics and focuses on what the call returns.

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 clearly identifies the resource as the nine capability dimensions and enumerates the metadata returned for each, including indicator counts, statuses, dataset version, and quoting contract. It also signals an entry point with "Start here," though it does not explicitly distinguish itself from the listed sibling tools.

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?

"Start here" gives clear first-use guidance, indicating this should be called before deeper lookups such as get_country or search_indicators. It does not state when not to use the tool or name a specific alternative, so it falls short of fully explicit routing guidance.

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