Skip to main content
Glama
Sign In
Convolut MCP Server

Convolut MCP Server

by expdal3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

update_context

Modify an existing context's title, content, tags, category, or favorite status in the Convolut Context Bank for better organization and relevance.

Instructions

Update an existing context with new title, content, tags, or metadata

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": {
      "context_id": "<context_id>"
    },
    "name": "update_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
context_idYesThe unique identifier of the context to update
titleNoNew title for the context
contentNoNew content for the context
tagsNoNew tags for the context
categoryNoNew category for the context
is_favoriteNoWhether to mark the context as favorite

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is an update operation but doesn't mention permission requirements, whether updates are partial or complete, if changes are reversible, error handling, or rate limits. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence that front-loads the core purpose. Every word earns its place with no redundant information or unnecessary elaboration.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens on success/failure, return values, or important behavioral aspects like whether all fields must be provided or if updates are partial. Given the complexity of updating a context with multiple fields, more contextual information 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 100%, so the schema already documents all 6 parameters thoroughly. The description mentions 'title, content, tags, or metadata' which maps to some parameters but omits 'category' and 'is_favorite' from its list. It adds minimal value beyond what the schema provides, meeting the baseline for high schema coverage.

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 ('Update') and resource ('an existing context'), and specifies what can be updated ('new title, content, tags, or metadata'). It distinguishes from 'create_context' by focusing on existing contexts, but doesn't explicitly differentiate from other siblings like 'consolidate_contexts' or 'plan_from_contexts'.

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 versus alternatives. It doesn't mention prerequisites (e.g., needing a valid context_id), when not to use it, or how it differs from other update-related operations that might exist among siblings.

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