Skip to main content
Glama

What Advisorn covers

list_topics
Read-onlyIdempotent

Lists all of Advisorn's questions and answers by topic and all glossary terms by group, with ids and links. Use when search finds nothing or to show what is covered.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: en, it, de or fr.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds that results include 'ids and links' and that content is grouped by topic and by group, which is useful result-shape context in the absence of an output schema, but it says nothing about size, ordering, or pagination.

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?

Two tight sentences: what it returns first, when to call it second. No filler or restated title.

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?

For a zero-required-parameter listing tool with full annotations and a fully documented schema, this is nearly complete — the returned content is described well enough that a missing output schema is not a real gap. Only the fallback relationship to about_advisorn could be clearer.

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 the sole 'lang' parameter is fully documented with its enum and default. The description adds nothing about language behavior (e.g., whether ids differ per language), so baseline 3 applies.

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 ('Lists') and two concrete resources (questions/answers organized by topic, glossary terms by group) plus the returned fields ('ids and links'), so an agent knows exactly what the call yields. The scope is clearly different from single-item siblings like get_answer and get_term.

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 triggers — 'Use when search finds nothing or to show what is covered' — and names the alternative ('search'). It does not state when NOT to reach for this over about_advisorn, but the positive guidance is concrete.

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