Skip to main content
Glama
Sign In
aparser-mcp

aparser-mcp

by izzipizzy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Task results

task_results

Fetch a one-time download URL for the output file of a completed A-Parser task, using the task's unique ID.

Instructions

Get a single-use download URL for a completed task's results file.

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": {
      "task_uid": "<task_uid>"
    },
    "name": "task_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_uidYesThe task id returned by add_task.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.2/5.0
Behavior4/5

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

Discloses the key behavioral trait that the URL is 'single-use'. Since no annotations exist, the description carries the full burden and does so well.

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?

Single sentence, front-loaded, no wasted words. Efficiently communicates the core function.

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

Completeness4/5

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

Adequate for a simple tool with one param and no output schema. Could explicitly state failure behavior if task not completed, but implied.

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?

The schema has 100% coverage for task_uid with basic description. The tool description adds value by explaining the URL's single-use nature and the requirement for a completed task.

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

Purpose5/5

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

The description clearly states the verb 'Get', the resource 'download URL for a completed task's results file', and the condition 'completed task'. It distinguishes from siblings like task_state and wait_task.

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?

Implied that it should be used after task completion, but no explicit guidance on when not to use or alternatives like task_state or wait_task for incomplete tasks.

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