Skip to main content
Glama

list_questions

Lists ranked S3 bibliometric research questions across three levels, showing priority and whether your dataset has the required columns for each question.

Instructions

The ranked research questions of the S3 method, in three levels: level 1 = the published S3 method (text similarity map; each question says whether it is in the S3 paper or an extension), level 2 (default) = + two-mode networks and knowledge graph (authors, institutions, journals, funders, layer overlap, homophily, citation direction), level 3 = + prediction (link prediction Q24-Q29, GNNs Q30-Q34; only when the user asks; include_prediction=True is the same as level 3). Shows priority and whether this dataset has the columns each question needs.

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

Input Schema

NameRequiredDescriptionDefault
levelNo
run_idYes
include_predictionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully reveals that the response is ranked, that each question is flagged as in-paper vs. extension, and that availability is checked against the dataset's columns — valuable behavioral context. It does not describe side effects, permissions, or cost, which for an unannotated tool leaves a gap.

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?

The core purpose is front-loaded in the first clause, and every parenthetical (question IDs, network types, GNNs) carries information about what the level adds. It is dense and slightly run-on, but no sentence is filler.

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?

With an output schema present, return values need not be explained, and the description still characterizes them (priority ranking, column-availability flags). The only real gap is the unexplained required run_id and the absence of any statement about read-only safety.

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?

Schema coverage is 0%, so the description must compensate, and it largely does: the three levels are spelled out concretely, and include_prediction is explicitly declared equivalent to level 3, removing ambiguity between two overlapping parameters. run_id, the only required parameter, is never explained, which is the sole meaningful omission.

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 — the ranked research questions of the S3 method — and enumerates its three levels with their contents, so an agent can tell what it retrieves. It does not explicitly contrast itself with siblings such as answer_question or run_s3_analysis, but the resource is distinctive enough to stand on its own.

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

Usage Guidelines3/5

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

It gives real selection guidance for the levels: level 2 is the default, and level 3 (prediction) should only be used 'when the user asks.' That is an explicit when-to-use constraint. However, it offers no guidance on when to call this versus other listing/analysis tools, nor any prerequisites beyond run_id.

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