Skip to main content
Glama
Promaxian

horizon-torn-mcp

by Promaxian

horizon_torn_getForumGeneric

Retrieve any Torn forum selection by name or ID, with filters for time range, sorting, pagination, and HTML stripping.

Instructions

Get any Forum selection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoselection id
toNoTimestamp that sets the upper limit for the data returned. Data returned will be up to and including this time
keyNoAPI key (Public).<br>It's not required to use this parameter when passing the API key via the Authorization header.
fromNoTimestamp that sets the lower limit for the data returned. Data returned will be after this time
sortNoSorted by the greatest timestamps
limitNo
offsetNo
commentNoComment for your tool/service/bot/website to be visible in the logs.
striptagsNoDetermines if fields include HTML or not ('Hospitalized by <a href=...>user</a>' vs 'Hospitalized by user').
timestampNoTimestamp to bypass cache or get the data in specific point in time
selectionsNoSelection names
Behavior2/5

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

No annotations are present, so the description carries the full burden. It only states 'Get,' implying read-only, but does not disclose permissions, rate limits, or side effects. Minimal behavioral information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single vague sentence. While concise, it is under-specified for an 11-parameter tool, lacking structure or prioritization of information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 11 parameters, no output schema, no annotations, and a vague description, it is insufficiently complete. It fails to explain what a 'Forum selection' is and how to effectively use the parameters.

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 description coverage is 82%, so the parameters are already well-documented. The description adds no additional meaning or context beyond the schema, aligning with the baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get any Forum selection' is vague and does not specify what a 'Forum selection' entails. There are many sibling forum tools with specific purposes (e.g., getForumAllThreads, getForumCategories), leaving the agent uncertain about what this tool retrieves.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool over the specific forum sibling tools. The agent receives no context on selection criteria or alternative recommendations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Promaxian/horizon-torn-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server