Skip to main content
Glama

VarynForge

by com.varynforge
OverviewDiscussionsAdmin

Download brief markdown

download_brief_markdown

Get a brief as inline markdown the host agent can use as a writing prompt. Pass format=markdown_inline, and channel (article default) to pick which of the suggestion’s per-channel briefs to render. Returns the brief assembled into a single markdown string capped at ~8K chars — markdown only; the structured fields are get_article_brief’s job and are omitted here.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  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",
-  "projectId",
-  "format"
-]New value: +[
+  "suggestionId",
+  "projectId",
+  "format",
+  "context"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Discloses the key behavioral traits: returns a single markdown string, ~8K char cap, markdown only, and omits structured fields. Although annotations don't declare read-only, the description is transparent about output and scope; it just doesn't discuss error cases or side effects.

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?

Three dense sentences, front-loaded with purpose, then invocation details, then output behavior. No filler or repetition of schema content.

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?

Given there is no output schema, the description adequately describes the return value, size cap, and format. It covers the main invocation choices and sibling routing; the only gap is not explicitly addressing how format values other than markdown_inline are handled, but the instructions are sufficient for a correct call.

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

Parameters4/5

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

Schema coverage is only 20%, but the description compensates by explaining format=markdown_inline and the channel parameter's default and per-channel role. The IDs are self-explanatory and context is already described in the schema, though the description could have tied them together more explicitly.

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 clear verb+resource ('Get a brief as inline markdown') and the intended use (writing prompt for the host agent). The final clause differentiates it from get_article_brief by saying structured fields are omitted, so an agent can tell which tool to pick.

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 explicit call guidance: pass format=markdown_inline and channel, notes article default. Names the sibling get_article_brief as the place for structured fields, providing a clear when/not-this-tool boundary.

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