Skip to main content
Glama
ToseaAI

mcp-ToseaAI

Official
by ToseaAI
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

tosea_get_presentation_full_data

Retrieve complete structured presentation data including outlines and slides from the ToseaAI MCP server for document-to-presentation workflows.

Instructions

Fetch full structured presentation data, including outlines and slides.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presentation_idYes

Implementation Reference

  • src/tools.ts:101-112 (handler)
    The tool 'tosea_get_presentation_full_data' is registered and implemented in src/tools.ts. The handler calls client.getPresentationFullData(presentation_id) and wraps the result.
    server.tool(
  "tosea_get_presentation_full_data",
  "Fetch full structured presentation data, including outlines and slides.",
  { presentation_id: z.string().uuid() },
  async ({ presentation_id }) => {
    try {
      return asToolResult(await client.getPresentationFullData(presentation_id));
    } catch (error) {
      throw wrapToolError(error);
    }
  }
);

Tool Definition Quality

B3.2/5.0
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. It states it 'fetches' data, implying a read-only operation, but doesn't disclose behavioral traits such as authentication requirements, rate limits, error handling, or whether it's idempotent. For a tool that likely accesses sensitive presentation data, this is a significant gap in transparency.

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 front-loads the key action and resource. Every word earns its place by specifying the scope ('full structured presentation data, including outlines and slides'), with no redundant or vague language.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no annotations, no output schema, and low schema coverage, the description is minimally adequate. It covers the purpose and scope but lacks details on behavior, parameters, and output. For a data-fetching tool with potential complexity (e.g., nested outlines and slides), more context would be helpful, but it meets a basic threshold.

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 input schema has 1 parameter with 0% description coverage, so the description must compensate. It doesn't mention the 'presentation_id' parameter explicitly, but the tool name and context imply it fetches data for a specific presentation. Since there are 0 parameters documented in the schema, the baseline is 4, as the description provides enough context to infer the parameter's purpose without adding specific details.

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 ('Fetch') and resource ('full structured presentation data') with additional scope details ('including outlines and slides'). It distinguishes from siblings like 'tosea_list_presentations' (which lists presentations) and 'tosea_get_permissions_summary' (which focuses on permissions). However, it doesn't explicitly differentiate from 'tosea_export_presentation' or 'tosea_render_slides', which might also retrieve presentation data in different formats.

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 guidance is provided on when to use this tool versus alternatives. For example, it doesn't clarify when to choose this over 'tosea_list_presentations' for metadata only, or 'tosea_export_presentation' for export formats. The description implies usage for fetching detailed data but lacks explicit context or exclusions.

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