Skip to main content
Glama

VarynForge

by com.varynforge

Get article suggestion

get_article_suggestion
Read-only

Get article suggestion details — metadata, cluster context, brief availability, registered derived assets (carousels, social posts), target keywords with volumes. Call get_article_brief for the full brief. Status semantics: generating_brief with briefQueuedAt set means the brief is QUEUED behind the free daily cap (forges automatically at reset); briefQueuedAt null means actively forging.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextYesOne sentence: what is the operator trying to achieve right now? Describe their goal, not this tool's purpose.
suggestionIdYes

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "One sentence: what is the operator trying to achieve right now? Describe their goal, not this tool's purpose.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "suggestionId"
-]New value: +[
+  "suggestionId",
+  "context"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true, so the description does not need to restate safety. It adds genuinely non-obvious behavior: what generating_brief with and without briefQueuedAt means, specifically queued behind the daily cap versus actively forging. That goes beyond what annotations or schema provide.

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?

Two sentences with no filler; the first sentence front-loads the resource and payload, and the second adds critical status disambiguation. Every clause earns its place.

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?

With no output schema, the description lists the major output groups and explains the non-obvious queued-brief semantics, which is enough for an agent to know what it will get. It does not spell out all possible statuses or exact field names, but nothing essential for a correct call is missing given the read-only annotation and self-explanatory parameter names.

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 description does not mention either parameter or explain how to get or validate suggestionId; the schema only provides format and pattern but no description, and the 50% coverage means the description was expected to compensate. 'context' is already described in the schema, but no additional meaning is added for the required ID.

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 opens with a specific verb and resource ('Get article suggestion details') and enumerates exact payload areas: metadata, cluster context, brief availability, derived assets, target keywords with volumes. It also separates itself from get_article_brief by directing full-brief requests there. This leaves no ambiguity about what the tool returns.

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?

It includes an explicit routing instruction: 'Call get_article_brief for the full brief,' which tells an agent when this tool is not the right choice. The status semantics for generating_brief also explain how to interpret a result that may be queued rather than ready. This is clear usage guidance for the most likely confusion among siblings.

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

All VarynForge toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools target a distinct resource and action, and the descriptions carefully cross-reference close alternatives (e.g., add_article_suggestion vs create_article_suggestion_with_input vs accept_idea). A few brief/read variants like get_article_brief, get_write_handoff, and download_brief_markdown could still be confused despite helpful explanations, so the set is not perfectly unambiguous.

Naming Consistency5/5

Tool names follow a highly consistent verb_noun snake_case pattern throughout: get_*, list_*, create_*, update_*, set_*, add_*, delete_*, start_*, expand_*, etc. Even the less common names like lint_draft and remap_asset are still clear verb_noun constructions.

Tool Count1/5

At 57 tools, this far exceeds the 50+ extreme threshold for a single MCP server. Even for a broad content workflow, the surface is overwhelming and would benefit from consolidation or splitting into focused servers.

Completeness4/5

The tool set covers the full content lifecycle: project setup, research runs, opportunity clustering, suggestion creation, brief generation, drafting, linting, publishing, reporting, and account management. Minor gaps exist—destinations and projects cannot be deleted via MCP, and there is no direct update for article suggestion metadata—but these are workable via the web UI or existing tools.

Resources