Skip to main content
Glama

List the desk's guides

list_guides
Read-onlyIdempotent

Frontier Desk's guides: one page per question an owner asks before a sale, a loan or a data licence. Each row carries the question the guide answers, a forty-to-sixty-word answer to it, the day the guide was last updated, and its address. Pass a slug from here to get_guide for the whole guide. Newest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many guides to return.
queryNoWords to find in a guide's title, question or description, for example "MSP" or "data room".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the row shape (question, a forty-to-sixty-word answer, last-updated day, address) and the newest-first ordering, which the annotations do not convey.

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?

Four short sentences, front-loaded with what the resource is, then row contents, then the get_guide handoff, then ordering. Every clause carries information; nothing is redundant with the 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?

There is no output schema, and the description compensates by enumerating the returned fields and sort order, which is what an agent needs to decide whether to call it. The only gap is the absence of guidance on query-matching semantics and result volume against the limit cap.

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%, with limit and query fully documented including defaults and bounds, so the schema carries the parameter burden. The description adds only 'Newest first' ordering context and does not explain query matching or paging behavior beyond what the schema states.

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?

States a specific verb and resource ('Frontier Desk's guides: one page per question an owner asks...') and defines the unit of return (one page per question). It also names the sibling get_guide and the exact handoff ('Pass a slug from here'), so an agent can distinguish the two without opening either schema.

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?

Gives explicit guidance for the follow-up step: use this to find a guide, then pass its slug to get_guide for the full content. It doesn't state when not to use it (e.g. versus other list_* siblings), so the routing is clear but not exhaustive.

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