Skip to main content
Glama
soke1556

zas-agent

by soke1556
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

zas_get_item

Fetch a single Zas channel item by ID: notes return as text and files are saved to a new path without overwriting existing files. Use it to retrieve one message or attachment safely.

Instructions

Fetch one item from a Zas channel. A note comes back as text; a file is written to disk. Returns the path written; it can differ from dest when a file with that name already exists. Writes a new file under dest (or the system temp directory); it never overwrites an existing file. The owner sees every item this agent sends with the >_ agent mark and this agent's name, on every device.

Input Schema

NameRequiredDescriptionDefault
idYesItem id, as `zas_list_items` reports it.
destNoWhere to write a file. A directory means "inside it". Defaults to a fresh temporary directory.
channelYesChannel name or id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.10.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden well: it discloses that files are written to disk, that dest defaults to a temp directory, that existing files are never overwritten, and that the returned path may differ from dest. It does not cover permissions, failure modes, or why the final sentence about what the owner sees applies to a fetch operation.

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?

The key purpose is front-loaded, but the file-writing behavior is repeated across multiple sentences and the final sentence about the owner seeing every item this agent sends is off-topic for a get tool. Those issues make it less tight than it could be.

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 three-parameter tool with no annotations and no output schema, the description explains the important side effect and return value well: notes come back as text, files are written without overwriting, and the written path is returned. It still leaves out error behavior and any channel access requirements.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds useful semantics for dest and the returned path, including temp default and non-overwrite behavior. It adds little beyond the schema for channel and id.

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 states a specific verb and resource: fetch one item from a Zas channel. It also clarifies the two payload modes, note as text and file to disk, which distinguishes retrieval-by-id from list-oriented siblings such as zas_list_items.

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?

It implies retrieval by item id, but does not say when to use this tool versus zas_list_items or direct-receive siblings. There are no explicit alternatives, prerequisites, or exclusions.

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