Skip to main content
Glama
Sign In
Proton Suite Agent

Proton Suite Agent

by Soluciones-Alexendros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Proton Drive format report

proton_drive_format_report
Read-onlyIdempotent

Analyzes file formats in a staging directory, providing a detailed report on file types and structures to aid in format assessment.

Instructions

Detailed analysis of file formats in the staging directory.

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

Input Schema

NameRequiredDescriptionDefault
staging_dirNo
response_formatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare read-only, open-world, and idempotent hints. The description adds no behavioral context beyond stating 'analysis', which is consistent but uninformative. No additional behavioral traits (e.g., dependency on other tools, rate limits) are disclosed.

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?

The description is a single sentence that quickly states the purpose, front-loading the key action. However, it is overly brief and does not include any parameter context or usage notes, sacrificing completeness for brevity.

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?

The description lacks contextual completeness. It does not explain what the analysis output looks like (e.g., counts, errors), does not indicate whether the staging directory must already exist or be populated, and does not clarify the relationship to sibling tools like proton_drive_list_files or proton_drive_audit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must provide parameter semantics, but it does not. It fails to explain the role of 'staging_dir' or the 'response_format' enum values (markdown vs json). This is a significant gap.

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?

The description states the tool performs detailed analysis of file formats in the staging directory, identifying the specific resource and scope. However, it does not explicitly distinguish this from sibling tools like proton_drive_list_files or proton_drive_audit, and 'analysis' is somewhat vague.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives like proton_drive_list_files or proton_drive_audit, nor does it mention any 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