Skip to main content
Glama
Sign In

CheckFlow

by io.checkflow
OverviewDiscussionsAdmin

Get standalone task files

get_standalone_task_files
Read-onlyIdempotent

The files attached to a standalone task, with their names, content types, descriptions, when and by whom each was uploaded, and a URL to download it. There is no file size. No field key, because a standalone task has exactly one place to put files rather than a template's several. A task with no files answers with an empty list. The URLs are not behind the API key -- the address is the secret -- so treat one as a credential.

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": {
      "taskKey": "<taskKey>"
    },
    "name": "get_standalone_task_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskKeyYesThe task's key, a GUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark the tool read-only and idempotent, and the description adds substantial behavioral context beyond that: returned fields, absence of file size, absence of field key for standalone tasks, empty-list behavior, and the security caveat that download URLs act as credentials.

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?

The definition is front-loaded with the core purpose, then efficiently adds only relevant behavioral details. Every sentence carries useful information for invocation or interpretation.

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 no output schema, the description still explains the return shape, empty-list behavior, and URL security semantics. For a simple one-parameter read operation, the agent has enough context to call and interpret it correctly.

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%, and the sole parameter taskKey is documented as a GUID in the schema. The description does not add additional meaning about the parameter beyond what the schema already provides.

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 identifies the resource, scope, and distinguishing feature: files attached to a standalone task. It also explicitly contrasts this with template tasks ('rather than a template's several'), helping the agent separate it from get_task_files.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when this tool applies: standalone tasks with attached files, including the empty-list case. It does not explicitly name get_task_files as the alternative for non-standalone task files, so it stops short of full when/when-not guidance.

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

All CheckFlow toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources