Skip to main content
Glama
Sign In
okf-tools

okf-tools

by hdean-ssp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

update_concept

Update an existing concept by modifying only specified fields, then automatically re-embed content and refresh the vector index.

Instructions

Update an existing concept in the bundle.

Applies only the provided fields to the concept, leaving unspecified fields unchanged. Re-embeds the content and updates the vector index.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "concept_id": "<concept_id>"
    },
    "name": "update_concept"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
typeNo
titleNo
contentNo
concept_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses mutation (update) and side effects (re-embed, index update). However, it does not mention error handling, authentication needs, or behavior if concept_id is invalid. Enough for basic understanding but not comprehensive.

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?

Two short sentences plus a two-line paragraph. No redundancy, front-loaded with purpose. Every sentence adds value.

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

Completeness3/5

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

An output schema exists (context signal), so return value details may be omitted. However, the description does not mention what the tool returns or confirm success/failure. The behavioral details are adequate for a mutation tool, but lacking error or result information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain individual parameters. Parameter names (title, content, type, tags) are somewhat self-explanatory, but 'type' and 'tags' lack clarity on constraints or allowed values. The partial update hint adds some value, but insufficient for a tool with 5 parameters.

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 'Update an existing concept in the bundle', specifying the verb and resource. It distinguishes from siblings like delete_concept and fetch_concepts, though the concept of a 'concept' is assumed.

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

Usage Guidelines4/5

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

The description explicitly mentions that only provided fields are applied, indicating a partial update behavior. It also notes side effects like re-embedding and vector index update. No explicit when-not-to-use guidance, but the context is clear.

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