Skip to main content
Glama

list_communities

Retrieve research communities from a cached Scopus analysis run, ranked by size with citation counts, year spans, saved labels, and quality metrics to review clustering results.

Instructions

All communities (largest first) with size, citations, year span, saved label, and QI/MI citation metrics when References were available.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "run_id": "<run_id>"
    },
    "name": "list_communities"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
min_sizeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the sort order and that QI/MI metrics appear only when References were available, which is genuinely useful conditional behavior. However, it says nothing about read-only semantics, pagination or result-size limits, or what happens with the defaulted min_size.

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?

A single dense sentence that front-loads the resource and ordering, then lists returned fields. Nothing is wasted, though the return-field enumeration partly duplicates the existing output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values do not need explaining, yet the undocumented min_size filter and the unstated run_id scoping are real gaps for a two-parameter query tool. Adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, so the description must compensate and does not: run_id is never mentioned, and min_size (default 2) is never explained or linked to the 'size' attribute that is described. The mention of 'size' only indirectly hints at the filter.

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 names a specific resource (communities) with explicit ordering (largest first) and enumerates the returned attributes, so an agent can distinguish it from get_community, which returns a single community. It never states the verb 'list' explicitly or that results are scoped to a run, but the intent is clear.

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?

There is no when-to-use guidance, no mention of when to prefer get_community or get_knowledge_tree instead, and no stated prerequisites. The agent must infer usage from the sibling names alone.

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