Skip to main content
Glama

Thread Kit: posts that fit every network

Example input and output of the two AI writers (free)

writing_examples
Read-onlyIdempotent

FREE. A hand-written example of what write_thread_from_article and write_short_video_script return, with the input that produced it. No model call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "writing_examples"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add context, and it does: the content is hand-written and static, no model is invoked, and the payload is tied to a specific input. It stops short of saying whether the sample is representative or version-specific.

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 short sentences with the cost signal ('FREE') front-loaded and the scope clarification last. Every clause carries information an agent needs to make a routing decision.

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 parameters and no output schema, the description carries the burden of describing the return, and it does so at a high level (example output plus originating input). It leaves open how the example is structured or whether multiple examples are included, which is a minor gap for a tool this simple.

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?

The tool takes zero parameters, so there is no parameter meaning to explain; the baseline applies. The description correctly implies no input is needed by presenting the tool as a fixed sample.

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 concrete resource (a hand-written example of the return values of write_thread_from_article and write_short_video_script) and its scope (includes the input that produced it). The clause 'No model call' separates it decisively from the two sibling writer tools it names.

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

Usage Guidelines3/5

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

The leading 'FREE' and 'No model call' imply the selection rule -- inspect the expected output shape without spending a model invocation -- but that rule is never stated as guidance. There is no explicit when-to-use/when-not phrasing or pointer telling the agent to call this before or instead of the real writers.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources