Skip to main content
Glama
Sign In
Heliyos MCP server

Heliyos MCP server

Official
by heliyos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update the knowledge base

heliyos_knowledge_update
Idempotent

Replaces the fixed knowledge base texts—business context, product information, pain points, value proposition, and qualification criteria—while keeping omitted fields unchanged for workers' next run.

Instructions

Changes the knowledge base's fixed texts: business_context, products_information, pain_points, value_proposition and qualification_criteria. What you leave out is kept, and the custom entries are untouched (use heliyos_knowledge_entries_set for those). Each text replaces the current one whole, so read it with heliyos_knowledge_get first when you mean to add to it. The workers read these on their next run. Returns structuredContent {knowledge}.

Input Schema

NameRequiredDescriptionDefault
pain_pointsNoThe customer problems the products solve, plain text or Markdown. An empty string clears it.
business_contextNoWhat the business does, plain text or Markdown. An empty string clears it.
value_propositionNoWhy customers choose these products, plain text or Markdown. An empty string clears it.
products_informationNoThe products and services, plain text or Markdown. An empty string clears it.
qualification_criteriaNoWhat makes a lead worth pursuing, plain text or Markdown. An empty string clears it.

Output Schema

NameRequiredDescriptionDefault
knowledgeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare it mutable, idempotent, non-destructive, and closed-world. The description adds important behavior beyond those hints: each provided text replaces the current one wholesale, omitted fields are preserved, custom entries are untouched, and workers pick up the changes on their next run. It also notes the returned structuredContent field.

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?

The description is four tight sentences, front-loaded with the operation and affected fields, then the replacement caveat, sibling routing, and worker-visibility note. Every sentence adds useful operational context with no filler.

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?

For a five-parameter optional update tool with full schema coverage and an output schema, the description covers the important gaps: partial-update behavior, wholesale replacement risk, how to read before appending, sibling-tool routing, and when workers see the changes. Nothing essential to correct invocation is missing.

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%, and the schema already describes each field, including that an empty string clears it. The description lists the same field names and adds overall replacement semantics, but does not add per-parameter meaning beyond what the schema provides, so the high-coverage baseline of 3 applies.

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 the specific verb and resource: it changes the knowledge base's fixed texts and names all five fields. It explicitly separates those fixed texts from custom entries handled by heliyos_knowledge_entries_set, so the agent can distinguish it from the sibling 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?

Gives explicit routing: use heliyos_knowledge_entries_set for custom entries, and use heliyos_knowledge_get first when adding to an existing text. It also explains that omitted fields are kept, clarifying partial-update behavior.

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