Skip to main content
Glama

re_embed_concept

Idempotent

Re-embed a single concept by its ID to refresh its vector representation and keep semantic search results aligned with updated concept data.

Instructions

Re-embed a single concept.

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

Input Schema

NameRequiredDescriptionDefault
concept_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say what gets overwritten, whether the operation is synchronous or queued, whether it costs API calls, or what happens if the concept has no source text to embed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with zero padding, so nothing is wasted. The problem is under-specification rather than verbosity; a sentence of behavioral detail could be added without bloat.

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?

An output schema exists, so return values need not be explained. Still, for a mutating, model-dependent operation, the definition omits what the operation actually does to stored state and when to trigger it, leaving the agent under-informed relative to the tool's complexity.

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% for the single required concept_id, and the description does not compensate by saying which identifier namespace it expects or what happens with an unknown id. The parameter name is self-explanatory enough to avoid a 1, but no real meaning is added.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb ('re-embed') with a specific resource ('concept') and scope ('single'), which is better than a tautology. However, it never explains what 'embedding' means in this system or how it differs from siblings like update_concept or record_concept_mapping, so the agent must infer the effect.

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?

There is no statement of when this tool should be used instead of update_concept or consume_concepts, no prerequisites, and no exclusions. The agent is left to guess whether re-embedding is required after an update or is an independent maintenance action.

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