Skip to main content
Glama
Promaxian

horizon-torn-mcp

by Promaxian

horizon_torn_getMyFactionAttacksSimplified

Retrieve your faction's simplified attack records. Filter attacks by direction (incoming/outgoing), time range, or ID.

Instructions

Get your faction's simplified attacks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoTimestamp that sets the upper limit for the data returned. Data returned will be up to and including this time
keyNoAPI key (Limited).<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
commentNoComment for your tool/service/bot/website to be visible in the logs.
filtersNoIt's possible to use this query parameter to only get incoming or outgoing attacks / revives. If not specified, this selection will return both incoming and outgoing attacks / revives. It's also possible to combine this with 'idFilter'. This filter allows using from/to to filter by ids instead of timestamps.
timestampNoTimestamp to bypass cache or get the data in specific point in time
Behavior2/5

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

With no annotations provided, the description carries full burden. It only says 'Get your faction's simplified attacks' without explaining what 'simplified' means, whether data is read-only, or any behavioral aspects like pagination or caching. This is insufficient for a tool with 8 parameters.

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

Conciseness4/5

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

The description is extremely concise at 4 words, with no unnecessary content. However, it lacks structure and is too brief to be fully informative, earning a score of 4 for conciseness but not for completeness.

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?

Despite high schema coverage, the description is incomplete for an 8-parameter tool with no output schema. It does not explain what 'simplified attacks' are, how the parameters relate, or what the return data contains. More context is needed.

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 88%, meaning most parameters have descriptions in the schema. The tool's description does not add any parameter-specific information, so it meets the baseline but does not enhance understanding beyond the schema.

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 clearly states the verb 'Get' and the resource 'faction's simplified attacks', indicating what data is retrieved. However, it does not distinguish this tool from closely related siblings like horizon_torn_getMyAttacksSimplified or horizon_torn_getMyFactionAttacks, reducing clarity.

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 versus alternatives. The tool name hints at 'simplified' vs full attacks, but the description fails to elaborate on this distinction or provide any usage context.

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