Skip to main content
Glama
Sign In
Aktar

Aktar

Official
by getaktar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search uploads

search_uploads
Read-only

Search Aktar upload history by file name, key, or destination in reverse chronological order; with no query, list recent uploads.

Instructions

Search Aktar's upload history by file name or key, newest first. Without a query, lists the latest uploads.

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": "search_uploads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return (default 20).
queryNoPart of the file name or key.
destinationNoOnly uploads to this destination (name or ID).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the meaningful behavior that results are ordered newest first and that an empty query degrades to a latest-uploads listing. It says nothing about pagination beyond the limit cap or about what a result 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?

Two tight sentences with the core scope front-loaded and the fallback behavior second. No filler or repetition of the title.

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?

For a simple three-parameter read tool with full schema coverage, the definition covers purpose, ordering, and the no-query case. The absence of an output schema means the shape of returned upload records is never described, which is the main remaining 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%, so all three parameters are already documented in the schema. The description reinforces the query semantics (file name or key) but adds no new detail for destination or limit. Baseline 3 applies when the schema carries the weight.

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 (search) and resource (upload history), plus the matching fields (file name or key) and sort order. It is clear enough to distinguish from siblings like list_bucket or list_destinations, though it never names an alternative explicitly.

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?

The sentence 'Without a query, lists the latest uploads' documents a degenerate usage mode, which is genuinely helpful. However, there is no statement of when to prefer this over the other listing tools, nor any exclusions or prerequisites.

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