Skip to main content
Glama

National Capability Benchmark

Read a known limit

get_limit
Read-onlyIdempotent

Read one known limit by id (A1, A2, ...): a place where the model produces a number that is wrong about the world. get_country lists the ids that apply to each score. Without an id, lists every limit with the dimensions and countries it covers.

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

Input Schema

NameRequiredDescriptionDefault
idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world semantics, so the bar is lower. The description adds genuine behavior beyond that: the two operating modes (single id vs. all limits) and a sketch of the returned content (dimensions and countries covered). Pagination or output size is unaddressed, keeping it short of a 5.

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?

Three compact sentences: purpose and id format first, provenance of ids second, fallback behavior last. Nothing is repeated and nothing is wasted.

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 single optional-parameter read tool with no output schema and safety already declared in annotations, this covers what an agent needs to call it correctly. The only missing piece is any hint about the shape or verbosity of the full-listing response when no id is given.

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?

Schema description coverage is 0%, so the description must carry the parameter meaning, and it does explain that id is an A-prefixed limit identifier and that omission switches to a full listing. That compensates for the coverage gap but provides no additional constraints beyond the schema's own regex pattern.

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?

Specific verb ("Read") plus resource ("one known limit by id") with the id format shown (A1, A2, ...) and a clarifying gloss on what a limit is. It also describes the no-id fallback mode, and explicitly points at get_country as the companion listing tool, so it is distinguishable from siblings.

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?

The description says where ids come from ("get_country lists the ids that apply to each score") and what happens when no id is supplied, which is real routing guidance. It stops short of stating when to prefer this over get_decision or compare_countries, so no explicit exclusions.

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