Skip to main content
Glama
Sign In
nexterm-mcp

nexterm-mcp

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nexterm_list_snippet_sources

Read-onlyIdempotent

Lists the sources backing stored snippets, helping you identify where snippet content originates before reading or managing it.

Instructions

List source-backed snippets.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is fully covered structurally. The description adds nothing beyond that — it never explains what "source-backed" means, whether the result is a filtered subset of snippets or a list of source records, or whether results are scoped per organization.

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 short sentence with no filler, so it is not verbose; however it is arguably under-specified rather than concise, and the single clause carries little information beyond the tool name.

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?

With no output schema and no parameters, the description is the only source of meaning, yet it leaves the central concept ("source-backed") unexplained and the relationship to sibling list tools unresolved. An agent cannot predict the result shape or know what separates it from nexterm_list_snippets.

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?

The tool takes zero parameters (EmptyInput), so there is nothing to document; baseline 4 applies. The description does not misleadingly imply hidden inputs, though it also does not mention that no filters are accepted.

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 verb+resource ("List ... snippets") is clear, but the qualifier "source-backed" is undefined and does not distinguish this tool from siblings like nexterm_list_snippets, nexterm_list_script_sources, or nexterm_list_sources. An agent cannot tell which of these to call from the description alone.

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 guidance on when to use this tool versus nexterm_list_snippets or the various *_sources tools, and no prerequisites or exclusions are stated. Usage must be inferred from the name.

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