Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getStorageFiles

List files in TestingBot storage with pagination controls, using limit and offset to retrieve manageable batches of stored files.

Instructions

List all files in TestingBot storage with pagination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getStorageFiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of files to retrieve (default: 10, max: 100)
offsetNoOffset for pagination (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.9/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 of behavioral disclosure. It conveys that this is a read/list operation with pagination, but says nothing about authentication requirements, page-size limits beyond the schema, ordering of results, or what a returned file entry contains.

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?

A single short sentence with the resource and pagination noted up front and no wasted words. It could have used one more clause for usage context, but nothing needs trimming.

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

Completeness3/5

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

For a zero-required-parameter read tool with a fully documented schema and no output schema, the description is minimally adequate: purpose and pagination are covered. It leaves the agent guessing about result ordering and what a storage file record looks like, which is a modest but real gap.

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 coverage is 100% and both parameters carry inline descriptions with defaults, ranges, and maximums. The description's mention of pagination adds only a framing cue, not syntax or behavioral meaning beyond the schema, so the baseline 3 applies.

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 (List) and resource (files in TestingBot storage) plus the pagination aspect, which distinguishes it from deleteStorageFile and from test-oriented siblings like getTests. It does not explicitly name a sibling to route against, but the resource scope is clear enough to identify the tool.

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 on when to choose this over storage-adjacent or file-listing siblings, and no prerequisites or exclusions stated. The only usage signal is the implicit 'list storage files' scope.

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