Skip to main content
Glama

Content Calendar Agent by Nova (CIVAI)

by co.civai.nova
OverviewDiscussionsAdmin

pdf__generate_pdf

Generate a PDF from a preview. Call with no args first: if multiple previews exist, returns needs_selection + previews (title + preview_id) — ask the user which one, then call again with preview_id. If only one preview exists, generates it immediately. Returns pdf_url when generated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
preview_idNoUnique preview_id from a prior preview_document result. Omit to list choices (when multiple) or generate the only/last preview.
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 burden and does well: it discloses the two response modes (needs_selection + previews list vs immediate generation) and the pdf_url return. It does not say whether generation consumes/invalidates the preview (relevant given the delete_preview sibling) or what happens if the preview_id is stale.

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?

Three tight sentences leading with the action, then the branching flow, then the success output. Every sentence carries operational information with no padding.

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?

No output schema exists, so the description must explain returns and it does (needs_selection, previews with title+preview_id, pdf_url). Combined with no annotations, the main remaining gap is error/failure behavior (e.g., no previews at all).

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% and both parameters are fully documented in-schema, so baseline 3 applies. The description reinforces preview_id's omit-to-list-or-generate semantics, but says nothing about notification_message beyond what the schema already states.

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?

States a specific verb+resource: 'Generate a PDF from a preview.' An agent can immediately tell this is a generation action distinct from the listing/fetch siblings, though no sibling is named explicitly for differentiation.

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?

Gives an explicit call sequence: invoke with no args first, branch on the result (multiple previews -> ask the user and re-call with preview_id; single preview -> generates immediately). This is a complete when/how procedure rather than an implied one.

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