Skip to main content
Glama

List the desk's public tool pages

list_public_pages
Read-onlyIdempotent

The tools Frontier Desk publishes for owners, each with what a reader gets from running it, plus the written pages behind them. Pass a route from here to get_public_page for that page's framing as written. The hub renders at https://www.frontierdesk.ai/tools. Every tool on this page runs on what you already know about the company and answers in one sitting. None of them asks for a data room, and none of them is a form that goes somewhere to be read later.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds real context about the catalog's nature: entries are self-contained, answer in one sitting, need no data room, and are not asynchronous forms. It does not describe the shape or size of the returned list, which is the main behavioral fact an agent still lacks.

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

Conciseness3/5

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

The functional content (what is listed, and the get_public_page handoff) is front-loaded in the first two sentences. The hub URL and the closing claim that every tool 'runs on what you already know' and 'answers in one sitting' are promotional framing that does little to help an agent decide to call or how to call it, so the text runs longer than the task requires.

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?

With no parameters, no output schema and full annotation coverage, the description only needs to convey what comes back and what to do with it. It does convey that routes are returned and routed onward to get_public_page, which is the key downstream dependency. It would be stronger if it indicated roughly how many entries or what fields each entry carries, but the essentials for correct invocation are present.

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?

The tool takes zero parameters, so there is nothing the description could clarify beyond confirming no input is required, which it effectively does by telling the caller to pick a route from the result rather than supply one upfront. Baseline for a parameterless tool 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 states a specific verb and resource: it lists the tool pages Frontier Desk publishes, each annotated with what a reader gets from running that tool, plus the written pages behind them. It separates itself from a single-page fetch by directing route lookups to get_public_page. The only blur is that 'pages' mixes two things (tool entries and the written pages behind them), which slightly muddies what exactly is enumerated.

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 gives an explicit handoff rule: take a route from this result and pass it to get_public_page for that page's framing. It also implicitly scopes use to surveying what the desk offers before drilling into one page. It stops short of a full when/when-not statement, e.g. no guidance on whether to prefer list_guides or list_markets for narrower inventories.

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