Skip to main content
Glama
boy-offi9-inc

HexForge Gateway

by boy-offi9-inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

summarize_text

Read-only

Condense long text or tool output into a concise summary using the Gateway's configured AI provider. Add optional instructions to tailor the result.

Instructions

Summarize text - e.g. long tool output - using the Gateway's configured AI provider, returning { summary } (up to about 512 tokens). The text and instructions are sent to that provider, which may be a remote API (Anthropic, OpenAI, Gemini, etc.) or a local model (Ollama), so don't pass anything you wouldn't send there. Errors if no provider is configured on the Gateway. Doesn't save anything to the knowledge base; to ask questions about a workspace's accumulated findings use chat_with_workspace instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe text to summarize. Must not be empty.
workspaceNoWorkspace name (not id). Created if it doesn't exist, and this call is recorded as a job in its history. Defaults to "default".
instructionsNoOptional extra guidance for the summary, e.g. "focus on network endpoints" or "one paragraph".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.7
    • addedInput schema / properties / content / description
      Added value: +"The text to summarize. Must not be empty."
    • changedInput schema / properties / instructions / description
      Previous value: -"Optional extra instructions for the summary"New value: +"Optional extra guidance for the summary, e.g. \"focus on network endpoints\" or \"one paragraph\"."
    • changedInput schema / properties / workspace / description
      Previous value: -"Workspace name (not id) - created automatically if it doesn't exist yet. Defaults to \"default\"."New value: +"Workspace name (not id). Created if it doesn't exist, and this call is recorded as a job in its history. Defaults to \"default\"."
  2. First observedv1.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare readOnlyHint/openWorldHint, but the description adds far more: the text is sent to a possibly-remote third-party provider with an explicit privacy warning, it errors when no provider is configured, output is capped at ~512 tokens, and it persists nothing to the knowledge base. These are exactly the behavioral traits structured fields can't convey.

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?

Purpose and return value are front-loaded, followed by the privacy caveat, error condition, and the routing alternative in tight sentences. Every sentence carries distinct, non-redundant information.

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

Completeness5/5

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

With annotations covering safety and a 100%-covered schema, the description still supplies the missing pieces an agent needs: output shape, provider/privacy implications, failure mode, and the alternative tool. Nothing material is absent.

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 coverage is 100%, so content/workspace/instructions are already documented. The description adds only the output shape ({ summary }, ~512 tokens) rather than parameter-level syntax. Baseline 3 is appropriate when the schema does the heavy lifting.

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 specific verb+resource (summarize text) and a concrete scope ('e.g. long tool output'), plus names the sibling it differs from (chat_with_workspace). An agent can distinguish it from the workspace-chat tool without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says when not to use it — 'Doesn't save anything to the knowledge base' — and names the alternative with its selecting condition: 'to ask questions about a workspace's accumulated findings use chat_with_workspace instead.' The 'e.g. long tool output' example gives a concrete use context.

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