Skip to main content
Glama

export_results

Writes CSV outputs for a completed bibliometric run—papers with community labels, community table, threshold scan, and citation matrix—to a chosen output directory.

Instructions

Write CSV outputs (papers with community + label, community table, threshold scan, citation matrix) to output_dir (default: the run folder).

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

Input Schema

NameRequiredDescriptionDefault
run_idYes
output_dirNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

A3.7/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 burden; it does disclose exactly which files are written and where they land by default, which is the most useful behavioral fact. It is silent on whether existing files are overwritten, whether the directory is created if missing, and what happens if run_id refers to an incomplete run — all material for a filesystem-writing operation.

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?

A single front-loaded sentence with a parenthetical default; the artifact list is packed efficiently and nothing is redundant or padded.

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

Completeness5/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 needn't be described, and the description covers the destination plus the full artifact inventory for a two-parameter tool. The only residual gap — overwrite/permission behavior — is modest relative to the schema richness on the output side.

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 should compensate. It explains output_dir meaningfully (default destination = the run folder), but the required run_id is never described — the agent must infer it identifies which analysis run supplies the data. One of two parameters is covered.

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 concrete verb (write) and enumerates the exact artifacts produced: papers CSV with community + label, community table, threshold scan, citation matrix. This is far more specific than the title alone and lets an agent distinguish it from a network-only exporter like export_networks. It stops short of explicitly naming that sibling as the wrong choice, so a 5 isn't earned.

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?

The default for output_dir ('the run folder') implies this is a post-analysis step, but there is no explicit when-to-use statement, no prerequisites (e.g., whether threshold_scan/citation data must already exist for all four files to be produced), and no exclusions or named alternatives among siblings.

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