Skip to main content
Glama

list_top_topics

Retrieve currently top or trending topics from the NodeLoc community. Use this tool to quickly see what's popular without needing authentication.

Instructions

List top/trending topics. Anonymous.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. 'Anonymous' is a useful auth-related behavior, and 'List' implies a read-only operation, but no further details are given about output format, ordering, limits, or side effects. It adds some value but leaves notable gaps.

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?

The description is two short, purposeful fragments: the action statement and the anonymity note. It is front-loaded with the core verb and resource, with no filler. Every word earns its place.

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 no-parameter list action, the description is largely sufficient. 'Anonymous' covers the main contextual prerequisite, and the tool name plus description make the expected return type (topics) clear. However, the criteria for 'top/trending' are not defined, which could matter in some contexts.

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 has zero parameters, so the schema is trivially complete at 100% coverage. The description does not need to explain parameter meaning, and the baseline of 4 applies. Nothing is missing in this dimension.

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: 'List top/trending topics.' The phrase 'top/trending' implicitly distinguishes this from siblings like list_latest_topics and list_category_topics, though it does not explicitly contrast with them. It is clear enough for an agent to understand the core function.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus list_latest_topics or list_category_topics. The 'Anonymous' note hints at authentication requirements but does not address selection criteria, sorting, or alternatives. An agent is left to infer the appropriate context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Patrick130306/nodeloc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server