Skip to main content
Glama

List desk notes

list_notes
Read-onlyIdempotent

Published desk notes, newest first: entry number, date (the day of the official action), published (the day the desk published the note), title, status, topic (cyber or sanctions), readers, source class, a one-line summary, and the note's URL. Pages with limit and offset; total is the count that matches, next_offset the offset of the next page. Filter by topic or reader as on the desk page.

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.
sinceNoOnly notes dated on or after this day (YYYY-MM-DD).
topicNocyber (exploited vulnerabilities, advisories, incident filings, the AI stack) or sanctions (everything else).
offsetNoHow many matching notes to skip, for the next page.
readerNoOnly notes written for this reader: sanctions-trade-finance-committee (Sanctions or trade-finance committee), owner-operating-executive (Owner or operating executive), platform-ai-stack-owner (Platform or AI-stack owner), deal-team (Deal team), credit-committee (Credit committee), cyber-underwriter (Cyber underwriter).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: only published notes are returned, ordering is newest-first, and pagination returns 'total' (matching count) and 'next_offset' (next page cursor). It does not discuss result caps or what statuses exist, keeping it from 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.

Conciseness4/5

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

Two sentences with no filler; the returned-field inventory is front-loaded and pagination semantics follow. The field list is dense but earns its place given there is no output schema.

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 compresses the return shape, ordering, and pagination contract into two sentences, which is adequate for a read-only list tool. What is missing is the relationship to sibling retrieval tools and whether temporal filtering uses action date vs publish date for both fields.

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%, so baseline is 3. The description adds modest value by clarifying that pagination uses limit/offset and that 'date' means the day of the official action (disambiguating what the 'since' filter compares against), but it does not explain the semantics of the enum filters beyond 'as on the desk page'.

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?

States a specific verb and resource ('Published desk notes, newest first') and enumerates the returned fields, so the agent knows exactly what it gets. It does not name the sibling it is not (search_notes for keyword lookup, get_note for a single note), so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: 'Filter by topic or reader' and paging hints tell the agent how to narrow results, but there is no explicit when-to-use-this-vs-search_notes guidance and no stated exclusions. An agent must infer that this is the browse/list path and search_notes is the query path.

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