Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Draft several collection items from a brief

draft_collection_items
Read-only

Write up to 12 new items for an existing collection from a short brief ("8 help articles about returns", "6 autumn menu dishes"), shaped by the collection's own fields. NOTHING IS SAVED: show the drafts to the user, then save the ones they keep with add_collection_items. Free to the user; limited per hour.

Input Schema

NameRequiredDescriptionDefault
briefYesWhat the items should cover, in the user's own terms — topics, tone, audience, specifics.
countNoHow many to write (default 6, max 12).
site_idYesThe site the collection belongs to
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
collection_typeYesThe collection's slug, as list_collections returns it (e.g. "blog", "menu", "products", "faqs").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint/destructiveHint, the description discloses the two behaviors that matter most for an agent: nothing is persisted (confirming the readOnly annotation) and the call is free but rate-limited per hour. Those cost/limit and non-persistence details are exactly the value-add annotations cannot express.

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?

Front-loaded with the core action and cap, followed by the non-persistence warning and the handoff to add_collection_items. No sentence is filler; even the parenthetical examples earn their place by disambiguating the brief format.

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?

For a 5-parameter drafting tool with no output schema, the description covers scope, limits, persistence behavior, and follow-up adequately. The only mild gap is that it never sketches what a returned draft looks like, though "show the drafts to the user" signals output is draft content rather than saved records.

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 brief, count, site_id, user_goal and collection_type are already documented in the schema. The description's brief examples give a feel for the input but add no syntax, format, or default information beyond what the schema states (max 12, default 6). Baseline 3 applies.

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?

States a specific verb (write/draft), a bounded resource (up to 12 new items for an existing collection), and an input form (a short brief). The examples ("8 help articles about returns", "6 autumn menu dishes") and the phrase "shaped by the collection's own fields" pin the tool's scope precisely and separate it from add_collection_items.

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?

The description spells out the workflow: draft first, show the user, then persist with add_collection_items. It names the sibling explicitly and gives the condition that selects it (items the user keeps), so the agent knows both when to use this tool and what to call next.

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

All Mondovo 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