Skip to main content
Glama

get_citation_structure

Reveal in-corpus citation flows between the largest research communities, with internal citation ratios and field citation shares, from a Scopus export containing References and EID columns.

Instructions

In-corpus citation flows between the largest communities (rows cite columns), plus QI (within-community citations / size) and MI (share of field citations). Needs References and EID columns in the export.

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": "get_citation_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes

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, and it does disclose one genuinely useful behavioral constraint — the required References and EID columns, which signals a likely failure path. It does not state that the operation is read-only, whether results are cached or persisted, or how 'largest communities' is bounded.

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?

Two dense sentences with no filler; the computed output leads and the prerequisite follows. Acronyms are expanded in place rather than assumed.

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 need not be described, and the core computation is explained adequately. What remains missing is the meaning of run_id and any sense of scale or selection rule for 'largest communities', which matters for interpreting the result.

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?

The single parameter run_id has 0% schema description coverage and the description never mentions it, so an agent gets no explanation of what a run refers to or where to obtain one. The one undocumented parameter means the description must compensate and it does not.

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 the specific analytical product — in-corpus citation flows between the largest communities, with rows citing columns — and defines the two derived metrics QI and MI inline. That is far more specific than a restatement of the name, though the operative verb is only implied by 'get' and nothing distinguishes it from analytical siblings like get_community or get_threshold_scan.

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?

The only conditional guidance is a prerequisite: the export must contain References and EID columns. There is no statement of when this analysis is appropriate versus other structure tools, no mention of alternatives, and no indication of what happens if the prerequisite is unmet.

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