Skip to main content
Glama

Content Calendar Agent by Nova (CIVAI)

by co.civai.nova
OverviewDiscussionsAdmin

pdf__get_preview

Preview PDF button. Call with no args first: if one draft exists, returns document_markdown; if multiple, returns needs_selection + previews — emit_display layout P (interaction_mode none) numbered picker only. NEVER collect_user_input or emit_display input for preview_id. After user replies with a number/title, call again with preview_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
preview_idNoOptional. Omit on first Preview PDF tap so the tool can list drafts. Pass only after the user picks from the numbered list (or when chat already has a clear id).
notification_messageNoShort user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "notification_message"
-]New value: +[]
  2. Changed1 schema field changed
    • changedInput schema / properties / notification_message / description
      Previous value: -"Short user-facing sentence for this action. Use {{var}} placeholders that replay will fill from API results (e.g. Added ₦{{money_delta}}. Balance ₦{{money_after}}.). Shown to the user if the follow-up reply fails."New value: +"Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names."
  3. Changed2 schema fields changed
    • addedInput schema / properties / notification_message
      Added value: +{
+  "description": "Short user-facing sentence for this action. Use {{var}} placeholders that replay will fill from API results (e.g. Added ₦{{money_delta}}. Balance ₦{{money_after}}.). Shown to the user if the follow-up reply fails.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "notification_message"
+]
  4. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the two possible return shapes, the required display layout (P, interaction_mode none, numbered picker), and prohibited follow-up calls. It omits any error/permission behavior, but for a UI-flow read tool the behavioral picture is unusually complete.

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?

Front-loaded with the tool's identity and sequenced instructions in a compact block with no filler. Some clauses are dense run-ons with internal jargon (layout P, interaction_mode none), which slightly hurts readability but not economy.

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?

There is no output schema, so the description must explain returns — it names document_markdown, needs_selection, and previews, which covers the branching outcomes. It does not describe the shape of items inside previews or failure modes, leaving a modest gap for a stateful interaction tool.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters are already documented with conditional usage notes (omit on first tap, pass after selection). The description restates that sequencing rather than adding new semantics such as format or validation rules, so the baseline 3 applies.

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?

Identifies the trigger (Preview PDF button) and the resource (PDF drafts), and immediately states the branching return behavior (single draft → document_markdown; multiple → needs_selection + previews). It is clearly distinct from siblings like pdf__list_previews and pdf__generate_pdf, though it never explicitly contrasts itself with them.

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

Usage Guidelines5/5

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

Explicitly prescribes the call sequence: no-args first to enumerate drafts, then a second call with preview_id only after the user replies with a number/title. It also states hard exclusions (NEVER collect_user_input or emit_display input for preview_id), which is exactly the when-not guidance an agent needs.

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

All Content Calendar Agent by Nova (CIVAI) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources