Skip to main content
Glama

tosea_list_export_files

Lists exported files for a ToseaAI presentation to manage and access available outputs from document-to-presentation workflows.

Instructions

List user-visible exported files for a presentation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presentation_idYes

Implementation Reference

  • Registration and implementation of the 'tosea_list_export_files' tool. It validates input using Zod and calls the 'client.listExportFiles' method.
    server.tool(
      "tosea_list_export_files",
      "List user-visible exported files for a presentation.",
      { presentation_id: z.string().uuid() },
      async ({ presentation_id }) => {
        try {
          return asToolResult(await client.listExportFiles(presentation_id));
        } catch (error) {
          throw wrapToolError(error);
        }
      }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'user-visible exported files', hinting at a read-only operation, but fails to detail permissions, rate limits, pagination, or output format. This leaves significant gaps in understanding how the tool behaves.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it highly concise and well-structured.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'user-visible' entails, the return format, or error handling, leaving the agent with insufficient information to use the tool effectively in a complex environment.

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 description implies the 'presentation_id' parameter is used to scope the listing to a specific presentation, adding context beyond the schema's 0% coverage. With only one parameter, this is sufficient to compensate, but it doesn't specify format or constraints beyond what the schema provides.

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 clearly states the action ('List') and resource ('user-visible exported files for a presentation'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'tosea_list_exports' or 'tosea_list_presentations', which might have overlapping functionality, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'tosea_list_exports' or 'tosea_redownload_export'. It lacks context about prerequisites, exclusions, or specific scenarios for its application, leaving usage unclear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ToseaAI/mcp-ToseaAI'

If you have feedback or need assistance with the MCP directory API, please join our Discord server