lore-mcp

snapshot_config

Capture and store a configuration snapshot with a name and data payload for persistent retrieval in a structured knowledge base.

Instructions

Snapshot current config

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": {
      "config_name": "<config_name>",
      "config_data": "<config_data>"
    },
    "name": "snapshot_config"
  }
}

Input Schema

Name	Required	Description	Default
`config_name`	Yes
`config_data`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.8.5May 28, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / config_data / additionalProperties
```
Added value: +true
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

First observedv0.7.0May 25, 2026

TDQS

D1.5/5.0

Behavior1/5

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

No annotations are provided, and the description fails to disclose any behavioral traits such as side effects, permissions, or output; it only restates the tool name, providing no value beyond the structured fields.

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

Conciseness2/5

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

The description is extremely short (three words), but it fails to convey useful information; it is under-specified rather than concise, and does not earn its place by aiding tool selection or invocation.

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

Completeness1/5

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

Given the lack of annotations, no parameter descriptions, and an output schema that is not described, the description is severely incomplete; it does not cover essential aspects like what the tool does, what the parameters mean, or what the output contains.

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

Parameters1/5

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

With 0% schema description coverage and no parameter explanation in the description, both 'config_name' and 'config_data' are left completely unexplained; the description adds nothing to understand their purpose or format.

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

Purpose2/5

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

The description 'Snapshot current config' suggests a verb+resource but is vague; 'snapshot' implies capturing existing state, yet the required input 'config_data' contradicts this by asking for data to be provided, causing confusion about the tool's actual function.

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?

No guidance on when or why to use this tool over siblings; the description offers no context or exclusions, leaving the AI agent to infer usage without any hints.

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