Skip to main content
Glama

Thread Kit: posts that fit every network

How each network counts post length (free)

network_rules
Read-onlyIdempotent

FREE. Limits, counting units and sources for X, Bluesky, Farcaster, Mastodon and Threads (Meta).

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": "network_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds two things beyond them: the cost signal ('FREE', meaningful in a server with a payment_options sibling) and the exact coverage scope — only five named networks are supported. It does not describe the shape of the returned data, but the scope disclosure is the operationally important part.

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 short fragments with no filler; the cost signal is front-loaded and the scope enumeration follows immediately. Nothing could be removed without losing information.

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 zero-parameter, read-only reference tool with no output schema, the description supplies what an agent needs: what data comes back and which networks it covers. A brief note on when to consult it versus the counting tools would make it fully self-sufficient.

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 nothing for the description to disambiguate and the baseline of 4 applies. The enumerated network list usefully clarifies what the implicit 'network' dimension of the answer covers.

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?

The description names the concrete content returned — limits, counting units, and sources — and enumerates the five networks covered (X, Bluesky, Farcaster, Mastodon, Threads). An agent can tell this is a static reference lookup rather than a computation tool like count_post_length. It lacks an explicit verb, and it doesn't name a sibling to differentiate against, which keeps it below a 5.

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?

There is no explicit when-to-use or when-not-to-use statement. The leading 'FREE' token implicitly contrasts this with paid siblings such as payment_options and hints it should be consulted before spending on length checks, but that routing logic is left for the agent to infer.

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