Skip to main content
Glama
Sign In
hortusfox-mcp

hortusfox-mcp

by tomfrenzel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Fetch chat messages

hortusfox_fetch_chat

Fetch recent workspace chat messages, optionally specifying the maximum number to return.

Instructions

Fetch recent workspace chat messages. Endpoint: /api/chat/fetch.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum messages to return (default 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / limit / minimum
      Added value: +-9007199254740991
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'recent' but does not specify sorting order, default behavior, or side effects. It does not clarify that the operation is read-only, nor does it disclose any behavioral traits like auth requirements or rate limits.

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 very concise, consisting of two sentences. However, the inclusion of the endpoint URL is extraneous for an AI agent and slightly reduces clarity. The main purpose is front-loaded.

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 simple tool with one parameter and no output schema, the description is minimal. It lacks details on default behavior, error cases, and how to handle larger result sets. Sibling fetch tools might have more context, but this one is lacking.

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 100% for the single parameter 'limit', which already describes it as 'Maximum messages to return (default 50)'. The description adds no additional meaning beyond the schema, so baseline of 3 is appropriate.

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?

The description clearly states 'Fetch recent workspace chat messages', specifying the action (fetch) and resource (chat messages). It distinguishes itself from sibling tools like hortusfox_add_chat_message and other fetch tools for different resources.

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?

The description provides no guidance on when to use this tool vs alternatives, no exclusions, no prerequisites, and no context about scenarios where it is appropriate or not.

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

Deploy Server

Other Tools