Skip to main content
Glama

save_community_labels

Store short topic labels for research communities in a bibliometric run so the labels persist with the run and appear in exports.

Instructions

Store short topic labels for communities, e.g. {"0": "Open innovation", "1": "..."}. Labels are saved with the run and included in exports.

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>",
      "labels": "<labels>"
    },
    "name": "save_community_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelsYes
run_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden. It does usefully disclose that labels are persisted with the run and surface in exports, which is real behavioral context. However, for a mutation tool it omits whether repeated calls overwrite existing labels, whether partial maps merge or replace, and any permission or failure conditions.

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 tight sentences with the concrete example front-loaded alongside the purpose. Nothing is padded, though the trailing '...' inside the example is slightly noisy.

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 no explanation. But for a nested-object mutation with zero annotation and zero schema description coverage, the definition leaves overwrite semantics and the run_id contract unaddressed, which an agent would need before calling safely.

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 compensate. The example communicates that labels is a key-to-string map of community identifier to short topic label, which is genuinely additive. But run_id gets no explanation at all, and the meaning of the numeric keys is only implied rather than stated.

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?

States a specific verb and resource: 'Store short topic labels for communities.' An agent can tell from the sibling list that this is the write-side counterpart to get_community/list_communities. It does not name a sibling explicitly, so it stops short of a 5.

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 when-to-use or when-not guidance, no prerequisites (e.g. that a run must exist or that communities must already be computed), and no indication of how this relates to run_s3_analysis or build_report. Usage is only inferable from the example payload.

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