Skip to main content
Glama

get_community

Retrieve central papers, abstracts, author keywords, and TF-IDF terms for one research community to interpret or label it; set abstract_chars=0 for titles only.

Instructions

Details for one community, to interpret or label it: the most central papers (eigenvector centrality, then citations) with abstracts, top author keywords and top TF-IDF terms. Set abstract_chars=0 to return titles only.

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>",
      "community_id": "<community_id>"
    },
    "name": "get_community"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
max_papersNo
community_idYes
abstract_charsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the ranking rule (eigenvector centrality, then citations), that abstracts are included and sized by abstract_chars, and the titles-only shortcut. It omits whether it is strictly read-only, what happens with an invalid run_id/community_id, and whether the paper list can be shorter than max_papers.

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?

Three tight sentences: purpose and output composition first, the degradation knob last. No filler, no restatement of the name, and the most decision-relevant facts are front-loaded.

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?

An output schema exists, so the description is not obliged to describe return values, yet it still summarizes them usefully. For a read-only, four-parameter tool the only real gap is the unexplained required run_id and any error behavior, which keeps it from a top score.

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 description coverage is 0%, so the description must supply parameter meaning; it explicitly defines abstract_chars including the 0 edge case and implies max_papers through 'the most central papers' with the default of 12. However, run_id and community_id — both required — get no explanation at all, so the agent must infer their meaning from names and sibling tools.

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?

The description names a specific verb/resource combination ('Details for one community') and then enumerates exactly what comes back: central papers ranked by eigenvector centrality then citations, with abstracts, top author keywords, and top TF-IDF terms. That content inventory distinguishes it from list_communities and the graph/tree siblings without needing to name them.

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?

It gives an explicit use context ('to interpret or label it'), which routes the agent toward labeling workflows such as save_community_labels, and offers a concrete mode switch ('Set abstract_chars=0 to return titles only'). It stops short of stating when not to use it or naming an alternative for a different view of a community.

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