Skip to main content
Glama

Get a frontier and its current record

get_frontier
Read-onlyIdempotent

Frontiers track the best known bound of a quantity (e.g. a kissing number) and who moved it. With an id: the frontier, its current lower and upper records (exact values as strings, never rounded) and its series. Without an id: the list of frontiers with their current records.

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_frontier"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoFrontier id, e.g. 'kissing-d11'. Omit to list all frontiers.
langNoLanguage of titles, labels and texts: 'fr' (French) or 'en' (English). Default 'en'. Use the user's language.en

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 establish that this is a read-only, idempotent, non-destructive operation with a closed world. The description adds meaningful behavioral context: record values are exact strings and never rounded, and each frontier includes its series and current lower/upper records. It does not discuss pagination or list-size behavior, but the added domain-specific transparency is substantial.

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 two sentences with no wasted language. It front-loads the core concept and then cleanly separates the with-id and without-id behaviors.

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?

There is no output schema, so the description must carry return-value information, and it does so reasonably: it names the frontier, the current lower and upper records, exact string formatting, and the series. It could say more about the shape of listed frontiers, but it is complete enough for an agent to call the tool correctly.

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 100%, so the schema already documents both parameters, including that omitting 'id' lists all frontiers and the valid language enum. The description reinforces the 'id' behavior but adds little beyond the schema and does not mention 'lang' semantics, so the baseline 3 is appropriate.

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?

The description states a specific verb and resource ('get a frontier') and immediately clarifies the domain object and the two operating modes: with an id versus without an id. An agent can understand what this tool returns without needing to infer from the name or title.

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?

It clearly explains the two usage modes: with an id to retrieve a specific frontier and its records, and without an id to list all frontiers. It does not explicitly state when to prefer alternatives, but the sibling tools are unrelated, so the conditional usage guidance is strong enough for correct selection.

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