Skip to main content
Glama
Sign In
OSF CLI Go

OSF CLI Go

by edithatogo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

osf_files_list

List files and folders in OSF Storage for a project or component, with an optional subpath filter.

Instructions

List OSF Storage files and folders for a project/component, optionally below a path.

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": {
      "id": "<id>"
    },
    "name": "osf_files_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOSF project/component id or URL
pathNooptional path below OSF Storage

Output Schema

NameRequiredDescriptionDefault
filesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. However, it only states the basic listing operation without detailing any traits like recursive listing, pagination, authorization needs, or whether the operation is read-only. Minimal transparency.

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 description is a single, succinct sentence of 14 words that conveys the essential function without any wasted verbiage. Front-loaded with the key action and resource.

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?

Given the presence of an output schema, return values are likely covered elsewhere. However, the description omits behavioral context (e.g., traversal mode, permissions, rate limits) and usage guidance, making it insufficient for an agent to fully understand the tool's behavior and when to invoke it.

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?

The input schema already describes both parameters (id and path) with 100% coverage. The description adds no new meaning beyond restating the schema, so baseline 3 applies.

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 action 'List' and the resource 'OSF Storage files and folders' for a project/component, and specifies optional path filtering. It effectively distinguishes from sibling tools like 'osf_components_list' or 'osf_contributors_list' which deal with different resources.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of when not to use it, such as for uploading or modifying files, nor any context about prerequisites or limitations.

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