Skip to main content
Glama

aw.transfer.guide

Read-only

Explicit native MCP file-transfer contract, bounds and client-history privacy. Discovery does not read your disk.

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": "aw.transfer.guide"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is largely covered. The description adds one real piece of context not in the annotations — that discovery performs no disk reads — which is meaningful for a file-transfer-adjacent tool, but it says nothing about output, side effects on client history, or how the 'bounds' are enforced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but the first sentence is a dense noun phrase without a subject or verb, which forces the reader to guess the action. Every word is arguably load-bearing only if the reader already knows the domain vocabulary.

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?

With no output schema and no parameters, the description carries the full burden of explaining what an agent gets back from a discovery call — a contract document, a capability list, a set of bounds — and it does not. The privacy assurance is useful but insufficient for a tool whose entire value is the content it returns.

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

Parameters4/5

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

The tool takes zero parameters, so the schema leaves nothing to explain and the baseline of 4 applies. The description does not need to compensate for any parameter ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a pile of nouns ('Explicit native MCP file-transfer contract, bounds and client-history privacy') with no verb stating what the tool actually returns or does. Only the second sentence hints at behavior ('Discovery does not read your disk'), implying this is a discovery/spec tool, but the core action is never named, and nothing distinguishes it from siblings like aw.status or aw.catalog.

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?

There is no explicit when-to-use guidance and no named alternative. At best, 'Discovery does not read your disk' implies it can be safely called up front, but an agent gets no condition for selecting this over aw.status or the aw.input.* family.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources