Skip to main content
Glama

get_act

Fetch an ARLIS act URL and save its metadata and full text as a local Markdown file, returning the saved path and heading structure for review.

Instructions

Fetch one ARLIS act URL and save it as a local markdown file.

Writes the act's plain-text metadata followed by its full text as markdown to <output_dir>/.md (default directory .arlis under PLUGIN_DATA, or the server working directory if PLUGIN_DATA is unset or empty). Returns only the absolute saved path, the metadata line range and a short line-numbered heading structure.

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": {
      "url": "<url>"
    },
    "name": "get_act"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesARLIS act url to save
output_dirNoDestination directory where the act’s Markdown file will be saved. Omit this parameter to use .arlis under PLUGIN_DATA, or the MCP server’s working directory if PLUGIN_DATA is unset or empty.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.9/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 well: it discloses the filename derivation (<numeric URL segment>.md), the destination resolution order (output_dir, then .arlis under PLUGIN_DATA, then the server working directory), and exactly what is returned. It omits overwrite/conflict behavior and network failure modes, which are the remaining gaps for a write-to-disk tool.

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?

Purpose is front-loaded in the first sentence, with save location and return value following in order of usefulness. The parenthetical default-directory explanation is long but necessary, and no sentence is filler.

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?

There is no output schema, and the description fully compensates by enumerating the return value: absolute path, metadata line range, and heading structure. For a two-parameter tool with no annotations, an agent has enough to call it and interpret the result.

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 100%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining how the URL determines the output filename and by restating the fallback chain for the destination directory. That helps an agent predict where the file lands.

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 (fetch one ARLIS act URL) plus the concrete effect (saved as a local markdown file), which makes the read-then-persist behavior unmistakable. It does not name or contrast with search_acts, so sibling differentiation is left to inference.

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?

Requiring a `url` argument implies this is used after obtaining an act URL, but the description never says so outright and never states when to prefer this over search_acts or what to do with multiple acts. Usage is implied rather than prescribed.

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

Deploy Server

Other Tools