Skip to main content
Glama

Plan a Slide - Form + Variant Candidates

plan_slide
Read-onlyIdempotent

Plan a PowerPoint slide before rendering: send a short brief and receive ranked candidates, a routing verdict, and input readiness to guide the next action.

Instructions

Plan a PowerPoint slide before rendering (free): send a short brief, get ranked candidates + a separated verdict — route (which slide: selected|needs_confirmation|ambiguous), input (can it render: ready|extractable_from_brief|needs_structured_data) and next_action. Free (one embedding). Then call create_slide with the chosen form(+variant). route.confidence: calibrated = measured P(route correct) with label high/medium/low cut on it; retrieval_score/retrieval_margin = the raw family-aggregated classifier values (not probabilities; margin can be negative when families contest); source = classifier | structural_router (LLM-rescued). candidate_margin on the top candidate = literal gap between the two shown scores.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNo
briefYes
escalateNoDefault true: on a low-confidence route the plan runs the SAME LLM rescue create_slide would (small COGS on that tail only), so plan and create always agree. Set false for a classifier-only, fully free plan (response then flags will_escalate + create_slide_behavior).
variant_policyNoproduction_safe: if the top routed variant is draft/beta, the family's demo-safe sibling leads and route reports both best_semantic and best_production_safe.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv5.5.4

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, but the description adds substantial extra context: free one-embedding cost, escalation behavior, calibrated confidence semantics, negative margin meaning, and source distinction. This goes well beyond the annotations.

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 front-loaded with the core purpose, then covers detailed response semantics that are necessary because no output schema exists. It is dense but not padded; the parentheticals are efficient rather than wasteful.

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?

The description thoroughly explains the returned verdict fields, confidence, retrieval scores, and next steps, compensating for the missing output schema. However, the 'top' parameter remains undocumented and the shape of the candidate ranking is only implied.

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

Parameters2/5

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

The input schema documents escalate and variant_policy, but the description does not explain the 'top' parameter at all, and only vaguely references 'a short brief.' With only 50% schema description coverage, the missing 'top' semantics is a meaningful gap.

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: plan a PowerPoint slide before rendering, returning ranked candidates plus a verdict. It explicitly hooks into create_slide for the actual creation step, which differentiates it from the sibling tool create_slide.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context: use this tool before rendering, it is free, and then call create_slide with the chosen form/variant. It does not exhaustively list when not to use the other siblings, but the workflow guidance is strong and unambiguous.

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

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/smartdatabrokers/slideforge-mcp'

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