Skip to main content
Glama

List the desk's published notes

list_notes
Read-onlyIdempotent

Frontier Desk's published notes, newest first: each one's title, the day it was published, its own address on the site, and its first sentence. Pass a slug from here to get_note for the whole note. The same notes render at https://www.frontierdesk.ai/intel, with an RSS feed at https://www.frontierdesk.ai/intel/rss.xml.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many notes to return, newest first.
sinceNoOnly notes published on or after this day, as YYYY-MM-DD. For example "2026-10-01".

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 the safety profile (readOnly, idempotent, non-destructive, closed-world), so the remaining burden is low. The description still adds real value by disclosing sort order, the per-item return shape, and the relationship to get_note. It does not mention the default page size, that results are capped, or whether a total count exists, which leaves some behavioral ambiguity.

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 sentences, zero filler: resource and ordering first, followed by return contents, then the routing hint and external surfaces. Every sentence carries information an agent needs and nothing is repeated from structured fields.

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 output schema, the description takes on the job of describing returned fields and does so for title, publication day, site address, and first sentence. The one soft spot is that the presence of a slug on each item is only implied by "pass a slug from here," and pagination beyond limit is unaddressed.

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 coverage is 100% and both parameters — limit and since with its YYYY-MM-DD example — are fully documented in the schema. The description reinforces ordering with "newest first" but adds no new semantics for since or limit, so this sits at the schema-carrying baseline.

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?

Opens by naming the exact resource and scope ("Frontier Desk's published notes, newest first") and then enumerates the returned fields, so the agent knows precisely what this fetches. It also distinguishes itself from get_note by stating that a slug from this list retrieves a single full note.

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 clearly signals browse-then-fetch usage by telling the agent to pass a slug from here to get_note, and it points to the human-facing page and RSS feed as alternate surfaces. It stops short of explicit exclusions — for example it never says to use search_notes when a query or filter is needed, even though that sibling exists.

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