Skip to main content
Glama

cli_ask

Interprets natural-language document instructions and executes PDF plans offline, with optional dry-run preview and output path control.

Instructions

AI Document Assistant: Interprets natural language instructions and executes document plans via offline NLP.

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": {
      "prompt": "<prompt>"
    },
    "name": "cli_ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputNoTarget input PDF path
outputNoOptional output path
promptYesNatural language query or instruction
dry_runNoDry-run only: interpret plan without executing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. 'Offline NLP' is a useful hint that no external model call is made, but the description says nothing about what files get written or overwritten, whether the tool mutates the input PDF, or that dry_run defaults to true — that last fact only lives in the schema.

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?

It is a single short, front-loaded sentence with no filler. The 'AI Document Assistant:' prefix is mildly redundant with the tool name but does not obscure the content.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool that accepts a free-form instruction and writes files, with no annotations and no output schema, the definition is far too thin. It never explains the scope of instructions understood, the relationship between input and output paths, or what a returned 'plan' looks like in dry-run mode.

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 100%, so the schema already documents input, output, prompt, and dry_run. The description adds no meaning beyond those fields, which is acceptable at full coverage but earns no extra credit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb (interprets, executes) and a resource (natural language document instructions), but 'document plans' is undefined and gives no sense of what operations are actually possible. It does not distinguish this tool from siblings such as document_workflow, cli_fill_batch, or batch_fill, so an agent cannot confidently route to it.

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?

There is no when-to-use guidance, no exclusions, and no named alternatives. An agent has no way to know whether this is the entry point for workflow-like operations or a fallback for one-off commands.

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