nc-mcp-server

list_conversation_presets

Read-onlyIdempotent

List available conversation presets with identifiers, names, descriptions, and settings, so create_conversation can start from the desired configuration.

Instructions

List the presets create_conversation can start from.

Returns: JSON list of presets with identifier (what create_conversation takes), name, description and the settings create_conversation applies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_conversation_presets"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.9.0Oct 1, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context by enumerating what each preset carries (identifier, name, description, applied settings) and flagging that the identifier is the value create_conversation accepts.

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

Conciseness4/5

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

Two short sentences that are front-loaded with the purpose; the Returns block is terse and each line earns its place. Slightly structural overhead but no filler.

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

Completeness4/5

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

For a no-arg read tool with an output schema, the definition covers purpose, the create_conversation linkage, and return shape. Nothing material is missing, though it could have noted that it must be called before create_conversation to obtain a valid preset identifier.

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

Parameters4/5

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

Zero parameters, so the baseline is 4. The description still adds value by explaining that the returned 'identifier' is the argument create_conversation takes, linking the output to a downstream call.

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?

States a specific verb and resource ('List the presets') and ties them to their consumer, create_conversation, so the agent understands what this resource is. It does not spell out the contrast against other listing tools like list_conversations, but the narrow 'presets' object makes it distinguishable enough.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: presets are 'what create_conversation can start from', so an agent can infer this is a discovery step before creating a conversation. There is no explicit when-to-use/when-not phrasing, nor any prerequisite or exclusion.

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

Deploy Server